An internal table can be specified as a data source data source of a query. This statement cannot be executed on all database systems, if the data from the internal table needs to be passed to the database.
Size comparisons can now be made between character-like data types and are no longer restricted to numeric data types.
The operator BETWEEN is also no longer restricted to numeric data types and SQL expressions can now be spceified on the right side.
The operator LIKE is now also supported.
The new type conversion functions BINTOHEX
and HEXTOBIN make it possible to convert byte strings to character strings (and the other way round) in
SQL expressions, which is not possible with a CAST expression.
In a subquery, it is now possible
to use an ORDER BY clause
and the additions UP TO,
OFFSET can be used after the clause. It is not possible to execute a subquery with an ORDER BY clause on all database systems
CDS access control
does not work for cross-client access. For this reason, the additions USING CLIENT and CLIENT
SPECIFIED can only be used in Open SQL in reads on CDS entities for which access control
is switched off using the annotation AccessControl.authorizationCheck.#NOT_ALLOWED
or the annotation WITH PRIVILEGED
ACCESS in the FROM clause of an Open SQL query.
Path expressions can only be evaluated if automatic
client handling is switched on. This cannot be done using CLIENT SPECIFIED in cases where path expressions are used that contain
associations whose target data source is client-specific
In path expressions in the FROM clause, the source data sources of the associations cannot be client-specific either.