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
New in 2.0.1: Negative integers are supported. Hexadecimal numbers are supported.
Negative numbers are not accepted.
The workaround is to specify negative values
-n as the
expression (0 – n).The operator ! is not accepted.
The equivalent of
!ISNULL(start_date) can be expressed
ISNULL(start_date) != 1true and false are not accepted,
-
use
1instead oftrue -
use
!=1instead offalse
null is not accepted, use instead the function
ISNULL(attribute)
External Keys are never
NULL, when undefined they are set to
0LIMIT, ORDER, GROUPBY, COUNT, SUM
Currently OQL does not
support LIMIT, ORDER, GROUPBY, COUNT, SUM, and many other
functions
2_5_0/oql/oql_limitations.txt ·
Last modified: 2018/12/19 11:40 by 127.0.0.1
