This shows you the differences between two versions of the page.
|
admin:features:segments:querying [2012/03/05 21:17] doc created |
admin:features:segments:querying [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration: Omnidex Features ====== | ||
| - | |||
| - | ===== Omnidex Segments ===== | ||
| - | |||
| - | [[admin:features:segments:home|Overview]] | | ||
| - | [[admin:features:segments:creating|Creating Segments]] | | ||
| - | **[[admin:features:segments:querying|Querying Segments]]** | | ||
| - | [[admin:features:segments:dropping|Dropping Segments]] | ||
| - | ---- | ||
| - | |||
| - | ==== Querying Segments ==== | ||
| - | |||
| - | Omnidex Segments can be referenced as criteria in a future query using the [[dev:sql:functions:segment:home|SEGMENT]] function. The SEGMENT function references the object name for any segment previously created or attached in the same connection. Alternatively, the SEGMENT function can reference a filename for a segment file created earlier by Omnidex or an external application. | ||
| - | |||
| - | Omnidex Segments can be used in conjunction with Omnidex Indexes. Index segments already contain index pointers, and can be incorporated into a search instantaneously. Data or delimited segments are processed like criteria, and require a search against the index to locate rows with those search values. | ||
| - | |||
| - | The following example shows several segments that were created in the previous page being referenced in a query using the SEGMENT function: | ||
| - | |||
| - | <code> | ||
| - | > ; Apply all temporary index segments, plus suppress any individuals that; | ||
| - | > ; were from two specific previous orders; | ||
| - | > create permanent delimited segment CURRENT_ORDER | ||
| - | >> physical "order_125.txt" | ||
| - | >> as (select INDIVIDUAL | ||
| - | >> from INDIVIDUALS | ||
| - | >> where INDIVIDUAL in (segment(PART_1), segment(PART_2)) and | ||
| - | >> INDIVIDUAL = segment(PART_3) and | ||
| - | >> INDIVIDUAL not in (segment('order_123.txt', 'DELIMITED'), | ||
| - | >> segment('order_124.txt', 'DELIMITED'))) | ||
| - | >> with delete; | ||
| - | Segment CURRENT_ORDER created with 18 rows | ||
| - | |||
| - | > ; Fulfill the query based on the final segment; | ||
| - | > select INDIVIDUAL, | ||
| - | >> BIRTHDATE, | ||
| - | >> CITY, | ||
| - | >> STATE | ||
| - | >> from INDIVIDUALS | ||
| - | >> join HOUSEHOLDS on INDIVIDUALS.HOUSEHOLD = HOUSEHOLDS.HOUSEHOLD | ||
| - | >> where INDIVIDUAL = segment(CURRENT_ORDER); | ||
| - | |||
| - | INDIVIDUAL BIRTHDATE CITY ST | ||
| - | ------------ ------------ ---------------------------- -- | ||
| - | 000400191550 1996-04-26 PHOENIX AZ | ||
| - | 000400575367 1996-11-19 PHOENIX AZ | ||
| - | 000400575369 2005-06-29 PHOENIX AZ | ||
| - | 000400575368 2004-07-30 PHOENIX AZ | ||
| - | 000403467441 2003-04-19 PHOENIX AZ | ||
| - | 000403467440 1997-02-28 PHOENIX AZ | ||
| - | 000403490448 1988-07-03 PHOENIX AZ | ||
| - | 000403490440 1988-04-14 PHOENIX AZ | ||
| - | 000800345452 1998-08-31 DENVER CO | ||
| - | 000800345451 1982-07-08 DENVER CO | ||
| - | 000802420583 1990-03-18 DENVER CO | ||
| - | 000802420582 1987-06-16 DENVER CO | ||
| - | 000802420584 1993-10-06 DENVER CO | ||
| - | 000803400688 1990-06-16 DENVER CO | ||
| - | 000803400689 1990-10-25 DENVER CO | ||
| - | 000803760388 2006-07-30 DENVER CO | ||
| - | 000803760386 1995-12-09 DENVER CO | ||
| - | 000803760387 1997-09-24 DENVER CO | ||
| - | |||
| - | 18 rows returned | ||
| - | </code> | ||
| - | |||
| - | |||
| - | ==== ==== | ||
| - | **[[admin:features:segments:creating|Prev]]** | | ||
| - | **[[admin:features:segments:attaching|Next]]** | ||
| - | |||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:admin:features:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||