Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Extended IntervalMatch problem

What is the problem with this example?

1 Solution

Accepted Solutions
johnw
Champion III
Champion III

You don't want the extended syntax here. The extended syntax is telling the system to merge the two tables based on IPNUmber (in Start/End range) and LocID. But there's no LocID on the Session table, so the merge doesn't work, and wasn't what you wanted anyway.

All you want to merge on is the IPNumber vs. the Start and End. That's just a regular syntax. To get the LocId back onto the Session table, you'll need a second join.

LEFT JOIN ([Session])
INTERVALMATCH (IPNumber)
LOAD
Start
,End
RESIDENT [IPLocation]
;
LEFT JOIN ([Session])
LOAD *
RESIDENT [IPLocation]
;

View solution in original post

2 Replies
johnw
Champion III
Champion III

You don't want the extended syntax here. The extended syntax is telling the system to merge the two tables based on IPNUmber (in Start/End range) and LocID. But there's no LocID on the Session table, so the merge doesn't work, and wasn't what you wanted anyway.

All you want to merge on is the IPNumber vs. the Start and End. That's just a regular syntax. To get the LocId back onto the Session table, you'll need a second join.

LEFT JOIN ([Session])
INTERVALMATCH (IPNumber)
LOAD
Start
,End
RESIDENT [IPLocation]
;
LEFT JOIN ([Session])
LOAD *
RESIDENT [IPLocation]
;

Not applicable
Author

Got it.

I thought, It should add LocID from range of Start/End for the IPNumber.

Thank you very much.