Powered by Zoomin Software. For more details please contactZoomin

DataDirect OpenAccess SDK Help

Conditions

  • Last Updated: May 12, 2026
  • 1 minute read
    • OpenAccess SDK
    • Version 8.1
    • Documentation

A condition specifies a combination of one or more expressions and logical operators that evaluates to TRUE, FALSE, or unknown.

You can use a condition in the WHERE clause of these statements:

  • DELETE
  • SELECT
  • UPDATE

You can use a condition in the HAVING clause of the SELECT statement.

The following table provides a description of the supported conditions.

Conditions

Condition Description
Simple comparison condition1 A simple comparison condition specifies a comparison with expressions or subquery results.
=, !=, <>, <, >, <=, <=
Group comparison condition1 A group comparison condition specifies a comparison with any or all members in a list or subquery.
[=, !=, <>, <, >, <=, <=] [ANY, ALL, SOME]
Membership condition A membership condition tests for membership in a list or subquery.
[NOT] IN
Range condition A range condition tests for inclusion in a range.
[NOT] BETWEEN
NULL condition A NULL condition tests for nulls.
IS NULL, IS NOT NULL
EXISTS condition An EXISTS condition tests for existence of rows in a subquery.
[NOT] EXISTS
LIKE condition A LIKE condition specifies a test involving pattern matching.
[NOT] LIKE
Compound condition A compound condition specifies a combination of other conditions.
CONDITION [AND/OR] CONDITION

1 Comparison conditions can be used to compare the values of LONGVARCHAR, WLONGVARCHAR, and LONGVARBINARY data. The values being compared must be the same data type. For example, you can compare a LONGVARCHAR value to another LONGVARCHAR value, but you cannot compare a LONGVARCHAR value to a LONGVARBINARY value.

TitleResults for “How to create a CRG?”Also Available inAlert