Omnidex Queries are typically specified using an Omnidex SQL SELECT statement.

Distinct can be applied to an entire select-item list or used within an aggregate function.

SELECT DISTINCT city, state FROM prospects

SELECT count(DISTINCT zip_code) FROM prospects

Result set limiters limit the rows returned by the select statement. The result set limiter processing is done AFTER the query has completed.

TOP n, EVERY n, RANDOM n

SELECT TOP 10 company FROM prospects

SELECT EVERY 20 company FROM prospects

SELECT RANDOM 10 company FROM prospects

These result set limiters do not order returned data in any way. Ordering is set by the ORDER BY clause.

Column names from one or more tables. These column names must be defined in the XML Catalog or the Environment Catalog.

SELECT company, contact, phone FROM customers

SELECT company, contact, order_date FROM customers, orders ...

An alias containing a space or special character must be quoted. Single or double quotes.

The AS keyword is optional.

SELECT company CO, contact 'Contact Name', phone "Phone Number" FROM ...

SELECT contact AS 'Contact Name', phone AS 'Phone #' FROM ...

SELECT customers.company, customers.contact, orders.order_date
  FROM customers, orders ...

SELECT A.company, A.contact, B.order_date FROM company A, orders B ...

SELECT customer_no, min(amount), max(amount), avg(amount)
  FROM orders GROUP BY customer_no

SELECT company, sum(amount) FROM ...

SELECT count(*), count(state) FROM ...

These functions can be used on literals or columns.

</code>

SELECT upper(company), upper(contact), current_date FROM ...

SELECT position('SYS' IN 'DYNAMIC INFORMATION SYSTEMS'), system_user FROM ...

Extended Functions

These functions can be used on literals or columns

SELECT $proper(company), $random(3) FROM ...

SELECT $soundex('database') FROM ...

SELECT 'Company Name: ', company, 'Contact Name: ', contact FROM ...

SELECT order_number, 'Discount: ', (quantity * amount)*.02 FROM ...

$ROWID returns the internal rowid. This is either the native rowid or the redefined rowid.

$ODXID is the Omnidex ID from the Omnidex indexes.

SELECT $ROWID, $ODXID, Company FROM ...

SELECT * FROM CUSTOMERS ...

SELECT c.*, o.* FROM CUSTOMERS c, ORDERS o ...

SELECT STATE, DESCRIPTION,
  (SELECT SUM(TOTAL) FROM ORDERS WHERE TAX_STATE='CO')
  FROM STATES WHERE STATE='CO'

The FROM clause allows the following retrieval types and join operations:

• Single Table
• Multiple Tables (Joins)
• Inner Joins - Join occurs in the where clause
• Outer Joins - Left Outer Join, Right Outer Join
• Nested Selects

SELECT * FROM CUSTOMERS

Join columns must have matching data types and lengths.

SELECT company, order_number FROM CUSTOMERS, ORDERS ...

Tables are joined in the WHERE clause. The join predicate is 'AND'ed to other WHERE criteria predicates.

SELECT company, order_number, status FROM customers, orders WHERE
   customers.customer_no = orders.customer_no AND orders.status='CANCELED'

Outer joins prevent the exclusion of records in one table that do not have records in the joined table.

SELECT company, order_number, status FROM customers c LEFT JOIN orders o ON
       c.customer_no = o.customer_no

SELECT company, order_number, status FROM customers c LEFT OUTER JOIN
       orders o ON c.customer_no = o.customer_no

SELECT company, order_number, status FROM customers c RIGHT JOIN orders o ON
       c.customer_no = o.customer_no

SELECT company, order_number, status FROM customers c RIGHT OUTER JOIN
       orders o ON c.customer_no = o.customer_no

select company, contact, state from customers c,
       (select distinct customer_no from orders where status='back') AS o
       where c.customer_no = o.customer_no and state!='co'

$CONTAINS

left_operand = right_operand (equal to)

left_operand < right_operand (less than)

left_operand > right_operand (greater than)

left_operand ⇐ right_operand (less than or equal to)

left_operand >= right_operand (greater than or equal to)

left_operand <> right_operand (not equal to)

left_operand != right_operand (not equal to)

left_operand in (value-list | Nested Select)

left_operand like right_operand_with_wildcard

exists (Nested Select) - MUST RETURN ONLY ONE COLUMN.

=, <, >, ⇐, >=, <>, like - Nested Select that GUARANTEES to return ONLY ONE ROW. MUST RETURN ONLY ONE COLUMN. in (Nested Select) - Can return 0 or more rows. MUST RETURN ONLY ONE COLUMN.

NOT, AND, OR with any of the above criteria predicates

left_operand and right_operand can contain any of the following:

• Columns
• Table Qualified Columns - table.column
• Column alias
• Literals
• Constants
• Expressions
• Wildcards
• $VALUES, $ROWID, $ODXID
• Omnidex Sentinel Character
• IS NULL - This will not be an optimized query!
• Use parenthesis to force order of precedence.

left_operand = right_operand (equal to)

SELECT company, contact FROM customers where company='systems'

SELECT customers.company, orders.order_no FROM customers, orders WHERE customers.customer_no=orders.customer_no AND (orders.status='shipped' OR orders.status='pending')

left_operand < right_operand (less than)

SELECT company FROM customers WHERE customer_no < 100

left_operand > right_operand (greater than)

SELECT customer_no, product_no FROM orders WHERE status='back' AND
       (quantity*amount) > 50 ORDER BY 1, 2

left_operand ⇐ right_operand (less than or equal to)

SELECT * FROM inventory WHERE onhand <= 10

left_operand >= right_operand (greater than or equal to)

SELECT company FROM customers WHERE customer_no < 100

left_operand <> right_operand (not equal to)

SELECT company, state FROM customers WHERE state <> 'CO'

left_operand != right_operand (not equal to)

SELECT company, state FROM customers WHERE state != 'CA'

left_operand in (value-list | Nested Select)

SELECT company, state FROM customers WHERE state IN ('A?', 'C?')

SELECT company, state FROM customers WHERE state NOT IN ('AZ', 'CA')

SELECT * FROM orders WHERE total > (SELECT avg(total) FROM orders)

left_operand like right_operand_with_wildcard

SELECT company, state FROM customers WHERE state like 'C?'

SELECT company, state FROM customers WHERE company = 'sys%'

exists (Nested Select)

Evaluates false if nested select returns 0 rows, true otherwise. In this example, all customer records will be returned.

SELECT c.company FROM customers c WHERE exists (SELECT * FROM orders o
       WHERE o.status='back')

=, <, >, ⇐, >=, <>, !=, like (Nested Select)

These selects MUST return only one column and only one row.

SELECT * FROM orders WHERE customer_no = (SELECT customer_no FROM customers
       WHERE company='Dynamic Information Systems')

SELECT customer_no, order_date, STATUS FROM orders WHERE product_no like
      (SELECT product_no FROM products WHERE product_no='SUP16210')

in (Nested Select)

SELECT distinct customer_no, status, product_no FROM orders WHERE product_no in
       (SELECT product_no FROM products WHERE product_name='monitor')

NOT, AND, OR

The following two statements return identical results, but note the placement of the NOT operator.

SELECT company, state FROM customers WHERE company='%systems or software'
       AND state NOT in ('AZ', 'CA')

SELECT company, state FROM customers WHERE company='%systems or software'
       AND NOT state in ('AZ', 'CA')

The next two statements return identical results, but note the differences in the WHERE clause with the Omnidex sentinel character and OR operator.

SELECT company, state FROM customers WHERE company='%systems or software'

SELECT company, state FROM customers WHERE company='systems' OR
       company='software'

The next two statements return companies located in Boulder CO, Boulder Creek CA, and Denton TX, but NOT Denver CO.

SELECT company, city, state FROM customers WHERE (city like 'boul%'
       AND state in ('CO', 'CA')) OR (city like 'den%' AND state != 'CO')

SELECT company, city, state FROM customers WHERE (city like 'boul%'
       AND state in ('CO', 'CA')) OR (city like 'den%' AND NOT state = 'CO')

Column Names from the Select List

Column Names Not in the Select List

HAVING Clause

Column Names From the Select List

select customer_no, sum(amount) from orders group by customer_no

select city, state, count(distinct company) from customers group by city, state

Column Names Not in the Select List

select status, sum(amount) from orders group by customer_no, status

select count(company) from customers group by state

Having

select customer_no, sum(amount) from orders
       group by customer_no having customer_no = 1001

select customer_no, sum(amount) from orders
       group by customer_no having status != 'shipped'

select status, sum(amount) from orders group by status having customer_no
       in (select customer_no from customers where company='systems')

Column Names

Column Alias

Select List Item Ordinal Numbers

Aggregates, Functions, Expressions

ASC, DESC

Column Names

SELECT company, contact, phone FROM customers ORDER BY company

SELECT company, contact, phone FROM customers ORDER BY company, contact

SELECT company, contact, phone FROM customers ORDER BY state

Column Alias

SELECT company CO, contact CT, phone PH FROM customers ORDER BY CO

SELECT company, contact, phone FROM customers ORDER BY CO, CT

Select List Item Ordinal Numbers

SELECT company, contact, state FROM customers ORDER BY 3

SELECT company, contact, state FROM customers ORDER BY 3, 1

Aggregates, Functions, Expressions

SELECT customer_no, sum(amount) FROM orders GROUP BY customer_no ORDER BY 2

SELECT customer_no, count(distinct order_no) FROM orders GROUP BY customer_no
       ORDER BY 2, 1

ASC, DESC

DESC (Descending) sorts will NOT be optimized, meaning they may increase the overall elapsed query time. ASC (Ascending) sorts may be optimized, depending on the index installation.

SELECT company, contact, phone FROM customers ORDER BY company asc

SELECT customer_no, count(distinct order_no) FROM orders GROUP BY customer_no
       ORDER BY 2 DESC, 1 ASC

Each individual JDBC Statement object and ODBC CLI HSTMT objects are created on their own cursors. Likewise, each Connection object in both types of applications are created on their own instances. Therefore, the use of the ON CURSOR and ON INSTANCE clauses is unnecessary. To switch between multiple cursors or instances, simply reference the appropriate object.

Syntax

statement [ON [CURSOR] n | [INSTANCE] n] [WITH options] statement

Required. Any valid SQL statement supported by Omnidex. ON

The ON CURSOR n clause is optional. If it is not specified, the SQL statement will be executed on the current cursor defined in the cursor parameter of the status array.

Required if specifying the cursor or instance number. Omit if using the default current cursor or instance. [CURSOR | INSTANCE]

Optional. The CURSOR and INSTANCE keywords are optional. n

Required if specifying the cursor or instance number. Omit if using the default current cursor or instance. This is the cursor or instance number that the current command will be executed on. Cursors and instances are numbered automatically as they are created. In OdxSQL, use the CURSORDISPLAY ON set option to automatically display the current cursor and instance numbers. [WITH options]

Optional. A comma separated list of options to use for the current statement.

ODXSQL Example

>SET CURSORDISPLAY ON

>connect /users/garment.env
Connected to /users/garment.env on instance 1, cursor 1

>connect / users/orders.env
Connected to /users/orders.env on instance 2, cursor 2

SELECT COMPANY, CONTACT, PHONE FROM CUSTOMERS WHERE STATE='CO' ON CURSOR 2
...

INSERT INTO CUSTOMERS (COMPANY, CONTACT) VALUES ('New Wave', 'Mr. Smith') ON CURSOR 1

The ON INSTANCE n clause can only be used by statements that do not require a cursor to be open. This includes statements like INSERT, INSERTINDEX, and many more. See the individual statement definitions for information on whether the statement uses an instance or a cursor. If omitted, the SQL statement will be executed on the instance owning the cursor passed in the cursor parameter of oaexecsql or in the instance member of the status array.

Rules for handling criteria strings in a WHERE clause:

Rule 1 - Sentinel Character The Omnidex Sentinel character is used in the right operand of a WHERE clause predicate and instructs Omnidex to consider the following criteria as Omnidex specific, as opposed to SQL specific. For example, company = '% systems or software' is the same as company = 'systems' or company = 'software'. The Omnidex Sentinel character is determined by the ENVIRONMENT …OMNIDEX SENTINEL clause in the environment catalog. The default is %. If the sentinel character is the leading character in the string and the predicate operator is = or IN, the criteria, minus the sentinel character, are submitted directly to Omnidex.

Rule 2 - Special Characters Fields installed with the KW (Keyword) option will be processed as follows: Leading and trailing characters that would be removed during indexing, are removed from the criteria string. When using the =, !=, LIKE and IN operators, embedded characters that are treated as keyword delimiters during indexing, are changed to a space. The space is the implied AND operator within Omnidex which enables a multiple-keyword search. For each keyword, leading and trailing characters that would be removed during indexing are removed and each keyword is processed individually according to the other rules. When using the >, <, >=, ⇐, and BETWEEN operators, the leading characters that are removed during indexing are removed. Criteria containing multiple keywords are quoted and regarded as a single keyword. Multiple-keyword searches are not supported with these operators.

Rule 3 - Quoted Operators Characters that are regarded as operators by the underlying indexing routines, are treated as literals and quoted as needed. Reserved words like AND, OR, NOT and TO are also quoted.

Rule 4 - Wildcard Characters When the criteria contains a wildcard character (default *, ?, #) and is used with the >, <, >=, ⇐ and BETWEEN operators, the criteria are quoted, causing the wildcard characters to be treated as literal characters. Wildcards are not supported with these operators.

Rule 5 - % and _ (Percent and underscore) Characters When used with the LIKE operator, the % and _ characters are ANSI SQL wildcard characters and are therefore converted to the corresponding Omnidex wildcard characters * and ? (or the corresponding custom wildcard characters as defined in the environment catalog). When used with = (equals), % is the default Omnidex Sentinel character. They are treated as literal characters when used with any other operator.

Rule 6 - Blank Criteria Criteria consisting of spaces or an empty string, is changed to a single space and quoted.

Rule 7 - Double Quotes Double-quotes tell Omnidex to treat characters as literals. Therefore: When all or part of the criteria string is double-quoted, Omnidex will process ANSI wildcards according to rule 5, provided the wildcards are outside of the quotes. Omnidex will not process special characters according to rules 3 and 4.

Rule 8 - $SOUNDEX If the criteria is from the $SOUNDEX function and the index being used has been installed with the ;SX option, the indexing token '!' will be appended to the original string from the $SOUNDEX function. The presence of this token will cause the indexing layer to process a Soundex search

The WITH clause is provided in the Omnidex Query language to allow an application to set options for a statement that are specific to that statement.

The WITH clause is appended to the end of an SQL statement, following the optional ON CURSOR|INSTANCE n clause, and contains a comma (or space) separated list of options that are to be applied to the processing of the SQL statement.

EXPORT COMPANY, CONTACT, PHONE FROM CUSTOMERS WHERE STATE='CO' WITH CHAR=AUTO

Syntax

statement [ON [CURSOR] n | [INSTANCE] n] [WITH option1[, option2]] statement

Required. Any valid SQL statement supported by Omnidex. ON [CURSOR | INSTANCE] n

Optional. See ON CURSOR ON INSTANCE for more details. WITH

Required if specifying options to be used for this current statement. Omit otherwise. options

Required if specifying options to be used for the current statement. Omit otherwise. This is a comma separated list of options valid for the current statement.

OdxSQL Example

Options passed in the WITH clause will be applied to all appropriate underlying OA API routines. For example, an EXPORT statement passed through oaexecsql will also cause calls to oaselect and oaexport. If the CHAR option is passed in the WITH clause of the SQL statement in oaexecsql, it will be applied to both oaselect and oaexport.

EXPORT COMPANY, CONTACT, PHONE FROM CUSTOMERS WHERE STATE='CO' TO CUSTS.TXT WITH CHAR=AUTO

It is possible to control which underlying functions a particular option is applied to. For example, the above example applies the CHAR option to both oaselect and oaexport, by default. However, this option can be applied to only one of these underlying functions by appending the function name, with a colon, to the front of the option, as shown:

EXPORT COMPANY, CONTACT, PHONE FROM CUSTOMERS WHERE STATE='CO' TO CUSTS.TXT WITH OAEXPORT:CHAR=AUTO

In this case, CHAR=AUTO is applied to oaexport but not oaselect.

Each of the underlying OA API routines support a different set of options.