Qlik Community

QlikView Scripting

Discussion Board for collaboration on QlikView Scripting.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

Inherited distinct in join

Hi to all!

Can some one tell me why distinct is inherited from previos load in join?

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?

Tags (2)
1 Solution

Accepted Solutions
Not applicable

Re: Inherited distinct in join

This has been acknowledged for a while now, and considered working as designed

http://community.qlik.com/thread/5762

6 Replies
Not applicable

Re: Inherited distinct in join

I see count=2 on test1 and count=3 on test2

Not applicable

Re: Inherited distinct in join

Yes. In test 1 dublicate rows are dropped and i dont understand why.

Test 1 is with distinct load in first table and the second is without.

But the data is the same in both cases.

MVP
MVP

Re: Inherited distinct in join

This is because your join resultant table is Groups1 which is qualified by DISTINCT before load. Therefore the table is loaded as distinct.

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.

Not applicable

Re: Inherited distinct in join

This has been acknowledged for a while now, and considered working as designed

http://community.qlik.com/thread/5762

Not applicable

Re: Inherited distinct in join

I know how to work around this, the question is why it works like this. It breaks the logic.

Not applicable

Re: Inherited distinct in join

It costed me a half day to determine this. This should be in QlikView help file. This behavior of distinct keyword is not intuitive.