QlikView Reference Manual.pdf - QlikCommunity - QlikView

08:00 4 Start of shift 2 D 07:23 11:43
11:43 5 End of production D 07:23 11:43
Back to Script Statements and Keywords (page 219).
IntervalMatch (Extended Syntax)
The extended IntervalMatch prefix to a Load (page 246) or Select (SQL) (page 262) statement is used for
matching discrete data to one or more dimensions that are changing over time. This is a very powerful and
flexible feature that can be used for resolving with slowly changing dimensions by linking the specific key
field(s) to the appropriate numeric intervals. The syntax is:
intervalmatch (matchfield,keyfield1 [ , keyfield2, ... keyfield5 ]
) (loadstatement | selectstatement )
matchfield is the field containing the discrete numeric values to be linked to intervals.
keyfield(s) are fields that contain the attributes that are to be matched using the interval.
loadstatement or selectstatement must result in a table where the first two fields contain the lower and upper
limits of each interval and the third and any subsequent fields contain the keyfield(s) present in the IntervalMatch
statement. The intervals are always closed, i.e. the end points are included in the interval. Nonnumeric
limits render the interval to be disregarded (undefined) while NULL limits extend the interval indefinitely
(unlimited). The intervals may be overlapping and values will be linked by all matching intervals.
In order to avoid undefined interval limits being disregarded, it is necessary to allow NULL values to map to
other fields that constitute the lower or upper limits to the interval. This can be handled by the NullAsValue
(page 255) statement.
Before the IntervalMatch statement, the field containing the discrete data points (Date in the example
below) must already have been read into QlikView. The IntervalMatch statement does not by itself read
this field from the database table.
Example:
Inner Join IntervalMatch (Date,Key) Load FirstDate, LastDate, Key resident
Key;
Back to Script Statements and Keywords (page 219).
Join
The join prefix joins the loaded table with an existing named table or the last previously created logical
table. The join is a natural join made over all the common Fields (page 169). The join statement may be
preceded by one of the prefixes Inner (page 239), Outer (page 255), Left (page 244) or Right (page 259).
join [ (tablename ) ]( loadstatement | selectstatement )
Examples:
Join Load * from abc.csv;
Join Select * from table1;
tab1:
Load * from file1.csv;
tab2:
243