Where clauses
Where-clauses in the One Identity Manager query language start with the WHERE keyword and contain a condition that the resulting data must match. Unlike SQL syntax, multiple Where clauses can be combined in a One Identity Manager query language query.
Examples of Where clauses
WHERE Lastname = 'Harris'
WHERE Lastname = 'Harris' AND Firstname = 'Clara'
WHERE [isnull(lastname, '') = N'Harris']
WHERE Lastname IN ('Harris', 'Basset')
WHERE XDateInserted IN RANGE LAST MONTH
Related topics
Search clauses
In the One Identity Manager query language the SEARCH keyword is used to search for all matching entries from the full text index. To use this type of clause, a full text index must be installed and accessible from the application.
SEARCH 'Search string'
Select clauses
The One Identity Manager query language Select clauses describe the data that is fetched from the underlying database. You define the minimum amount of returned data. The object layer can select more data to meet arbitrary requirements. An example is the primary key, which is always selected, or special columns like the X columns.
Multiple select clauses can be combined into one query.
Different variations of the Select clause are supported.
Selecting specific columns of a table
SELECT COLUMNS <list of columns>
Example
FROM Person
SELECT COLUMNS Firstname, Lastname, CentralAccount
Select all columns of a table
SELECT ALL
Selecting all display values of a table
SELECT DISPLAYS
Display columns that are selected are:
In the case of returned entries, the table's display pattern and the display pattern (long) can be overwritten by a display value clause. For more information, see Display value clauses.
Selecting the table's display pattern
SELECT DISPLAYPATTERN
Selects only the columns from the table's display pattern or DISPLAY clause if it is used. This can provide improved performance over SELECT DISPLAYS because fewer columns are selected.
Select all columns of a table that are not marked as a BLOB field
SELECT NONLOBS
Selects all columns of the table that are not marked as a very long binary object or text object by the DialogColumn.IsBlobExternal column.
A matching entry exists
EXISTS
Determines whether an entry exists that fulfills the WHERE clause. The Exist clause overrides all other Select clauses except the Count clause.
Determine the number of matching entries
COUNT
Counts the entries that fulfill the where clauses. The Count clause overrides all other clauses.
Order by clauses
The Order by clause in the One Identity Manager query language, specifies the order in which entries are returned.
ORDER BY <list of columns>
The column order can be specified by
When display values are selected, a default order by clause is created for the display columns.
Examples of Where clauses
ORDER BY Lastname, Firstname
ORDER BY EntryDate DESC
You can specify fallback columns, which will be used for sorting if the previous values are NULL. These fallback values are specified by the null coalescing operator ??.
Examples for a fallback column's data
ORDER BY DisplayName ?? CN
ORDER BY DisplayName ?? CN DESC, XDateInserted