topic Re: Inherited distinct in join in QlikView https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515875#M693371 <HTML><HEAD></HEAD><BODY><P>Yes. In test 1 dublicate rows are dropped and i dont understand why.</P><P>Test 1 is with distinct load in first table and the second is without.</P><P>But the data is the same in both cases.</P></BODY></HTML> Thu, 27 Jun 2013 11:58:20 GMT 2013-06-27T11:58:20Z Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515873#M693369 <HTML><HEAD></HEAD><BODY><P>Hi to all!</P><P></P><P>Can some one tell me why distinct is inherited from previos load in join?</P><P>See the attachment. I am loading first table distinct and then loading second table NOT distinct and joining them. The result table turns out distinct too. Why?</P></BODY></HTML> Thu, 27 Jun 2013 11:08:52 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515873#M693369 2013-06-27T11:08:52Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515874#M693370 <HTML><HEAD></HEAD><BODY><P>I see count=2 on test1 and count=3 on test2</P></BODY></HTML> Thu, 27 Jun 2013 11:54:23 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515874#M693370 2013-06-27T11:54:23Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515875#M693371 <HTML><HEAD></HEAD><BODY><P>Yes. In test 1 dublicate rows are dropped and i dont understand why.</P><P>Test 1 is with distinct load in first table and the second is without.</P><P>But the data is the same in both cases.</P></BODY></HTML> Thu, 27 Jun 2013 11:58:20 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515875#M693371 2013-06-27T11:58:20Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515876#M693372 <HTML><HEAD></HEAD><BODY><P>This is because your join resultant table is Groups1 which is qualified by DISTINCT before load. Therefore the table is loaded as distinct.</P><P></P><P>See the attached file, if you take a resident of the Groups1 table and then JOIN, you would get different result, because your resultant table is not qualified by DISTINCT there.</P></BODY></HTML> Thu, 27 Jun 2013 12:23:35 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515876#M693372 tresB 2013-06-27T12:23:35Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515877#M693373 <HTML><HEAD></HEAD><BODY><P>This has been acknowledged for a while now, and considered working as designed</P><P></P><P><A _jive_internal="true" class="loading" href="https://community.qlik.com/thread/5762">http://community.qlik.com/thread/5762</A></P></BODY></HTML> Thu, 27 Jun 2013 12:24:18 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515877#M693373 2013-06-27T12:24:18Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515878#M693374 <HTML><HEAD></HEAD><BODY><P>I know how to work around this, the question is why it works like this. It breaks the logic.</P></BODY></HTML> Thu, 27 Jun 2013 12:29:17 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515878#M693374 2013-06-27T12:29:17Z Re: Inherited distinct in join https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515879#M693375 <HTML><HEAD></HEAD><BODY><P>It costed me a half day to determine this. This should be in QlikView help file. This behavior of distinct keyword is not intuitive.</P></BODY></HTML> Thu, 27 Jun 2013 12:36:09 GMT https://community.qlik.com/t5/QlikView/Inherited-distinct-in-join/m-p/515879#M693375 2013-06-27T12:36:09Z