Databases Reference
In-Depth Information
Notice how the rows from the second table were appended to the first table, and that
non-matching fields have all been given null values.
Make it explicit too
As you can see in the example code, the
CONCATENATE
statement also supports explicitly specifying which table to
concatenate to. For the same reasons named with the
JOIN
statement, it is a good idea to always do this.
The NOCONCATENATE statement
When two tables share the exact same columns, QlikView will automatically
concatenate them. For example, when looking at the following code we could
assume that the result would be two tables,
Table1
and
Table2
.
Table1:
LOAD * INLINE
[
A, B, C
1, 1, 1
2, 2, 2
3, 3, 3
];
Table2:
LOAD * INLINE
[
A, B, C
4, 4, 4
5, 5, 5
6, 6, 6
];
However, in reality, as both tables share the exact same columns, QlikView will
implicitly concatenate
Table2
onto
Table1
. The result of this script is a single table.
We can prevent this from happening by prefixing the
LOAD
statement for
Table2
with the
NOCONCATENATE
statement. This statement instructs QlikView to create a
new table, even if a table with the same columns already exists.
