The join and keep prefixes can be preceded by the prefix inner.If used before join it specifies that an inner join should be used. The resulting table will thus only contain combinations of field values from the raw data tables where the linking field values are represented in both tables. If used before keep, it specifies that both raw data tables should be reduced to their common intersection before being stored in QlikView.
Syntax:
Inner ( Join | Keep) [ (tablename) ](loadstatement |selectstatement )
Arguments:
| Argument | Description |
|---|---|
| tablename | The named table to be compared to the loaded table. |
| loadstatement or selectstatement | The LOAD or SELECT statement for the loaded table. |
Example 1:
|
Table1 |
- |
|---|---|
|
A |
B |
|
1 |
aa |
|
2 |
cc |
|
3 |
ee |
|
Table2 |
- |
|---|---|
|
A |
C |
|
1 |
xx |
|
4 |
yy |
QVTable:
SQL SELECT * From table1;
inner join SQL SELECT * From table2;
|
QVTable |
- |
- |
|---|---|---|
|
A |
B |
C |
|
1 |
aa |
xx |
Example 2:
QVTab1:
SQL SELECT * From Table1;
QVTab2:
inner keep SQL SELECT * From Table2;
|
QVTab1 |
- |
|---|---|
|
A |
B |
|
1 |
aa |
|
QVTab2 |
- |
|---|---|
|
A |
C |
|
1 |
xx |
The two tables in the keep example are, of course, associated via A.
