Known issues and limitations
New since 2.3.0: New constrains on OQL formatting due to Request optimization:
If the user has Allowed organizations
defined, then
this query will fail for him
SELECT l FROM Organization AS child JOIN Organization AS root ON child.parent_id BELOW root.id JOIN Location AS l ON l.org_id = child.id
Use instead
SELECT Location AS l JOIN Organization AS child ON l.org_id = child.id JOIN Organization AS root ON child.parent_id BELOW root.id
The operator ! is not accepted.
The equivalent of
!ISNULL(start_date)
can be expressed
ISNULL(start_date) != 1
true and false are not accepted,
-
use
1
instead oftrue
-
use
!=1
instead offalse
null is not accepted, use instead the function
ISNULL(attribute)
External Keys are never
NULL
, when undefined
they are set to
0
LIKE
The syntax for LIKE is LIKE “%abc%”. To escape a character, you
have to prefixe the character by \. (SELECT Contact WHERE name LIKE
“%d\”a%“)
To escape %, you have to prefixe it by \\. (SELECT VirtualMachine
WHERE name LIKE ”%d\\%a%“)
LIMIT, ORDER, GROUPBY, COUNT, SUM
Currently OQL does not
support LIMIT, ORDER, GROUPBY, COUNT, SUM, and many other
functions
2_6_0/oql/oql_limitations.txt ·
Last modified: 2020/02/05 11:42 (external edit)