Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
this might be a very simple question - at least it is something very basic - but I'm always unsure about this and I usually go the other way just to be on the safe side:
When I have a LOAD consisting of two parts - so there is a second LOAD with CONCATENATE - and I want to build a "secondary" calculated field already building on a calculated field in the LOADs - can I do a PRECEDING LOAD before the first one? Will that capture all of it, or just the first half?
It is certainly more secure to use a RESIDENT afterwards, but still I wonder, this would be faster if it works ...
To illustrate: My LOAD looks like
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Tablename:
LOAD
bla1
bla2
FROM
blubber1;
Concatenate
LOAD
bla1
bla2
FROM
blubber2;
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
What I'd like to do is something like
Tablename:
LOAD
blabberdibla;
LOAD
bla1
bla2
FROM blubber1;
CONCATENATE
LOAD
bla1
bla2
FROM blubber2;
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Would that work? Would QlikView do both parts of the LOAD before putting the PRECEDING LOAD on top of it?
Thanks a lot!
Best regards,
DataNibbler
why not just test it:
LOAD 2*Field as Field;
LOAD * INLINE [
Field
10
15
25
];
Concatenate
LOAD * INLINE [
Field
1
2
3
];
result:

But I think resident loads are mostly faster... a preceeding load on top works only for the load before...
why not just test it:
LOAD 2*Field as Field;
LOAD * INLINE [
Field
10
15
25
];
Concatenate
LOAD * INLINE [
Field
1
2
3
];
result:

But I think resident loads are mostly faster... a preceeding load on top works only for the load before...
Thanks Robin!
So I guess I will go with the PRECEDING LOAD wherever it is necessary.
Thanks a lot!
Best regards,
DataNibbler
... I never thought about your question before, because I prefer resident loads ...
You're right - I build applications for other people myself and I usually try to make it possible for other developers to understand my code - what is done at which point, how and why ...
Of course then a RESIDENT LOAD is nearly always preferable because PRECEDING LOADs are a bit hard to read ...