Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
This feels pretty beginner, but I'm not sure what the answer is, so please let me know. If I have script like the following:
Left Join (TableA)
TableB:
Load FRUITS, VEGETABLES from ...
TableC:
Load FRUITS, VEGETABLES from ...
Will table B first join to table A, and then a separate table C will load into memory
OR
Will table B and C concatenate and then the result will be joined with TableA
?
In this case I would prefer that the concatenation occurs before the joining, but I suspect that it wouldn't.
(by the way, I can do a workaround with Residents - no problem - I just want to make sure I understand how the order of operations works in script loads).
You are right, Table B will first join and then TableC will be created.... that's just how the order of operation work in Qlik View or Qlik Sense and I guess work around that you mentioned might be the only option here...
You are right, Table B will first join and then TableC will be created.... that's just how the order of operation work in Qlik View or Qlik Sense and I guess work around that you mentioned might be the only option here...
As far as you know there is no way to do something like:
Left Join (TableA)
(
TableB:
Load FRUITS, VEGETABLES from ...
TableC:
Load FRUITS, VEGETABLES from
)
To force the concatenation before the join?
I don't think so... you will have to do this just like you think
TempTable:
Load FRUITS, VEGETABLES from ...
Concatenate(TempTable)
Load FRUITS, VEGETABLES from ...
Left Join (TableA)
LOAD *
Resident TempTable;
DROP Table TempTable;
Yeah, figured. Thought I'd give it a shot thought. Thanks.