SAP NetWeaver AS ABAP Release 752, ©Copyright 2017 SAP AG. All rights reserved.
ABAP - Keyword Documentation → ABAP - Release-Specific Changes → Changes in Releases 7.5x → Changes in Release 7.52 →
Open SQL in Release 7.52
1. Internal tables as data sources
6. ORDER BY and UP TO, OFFSET in subquery
7. Cardinality in LEFT OUTER JOIN
8. FOR ALL ENTRIES and strings in the SELECT list
9. Strict mode in the syntax check
11. Replacement service for Open SQL
Internal Tables as Data Sources
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.
Relational Expressions
The following is now possible for conditions in expressions:
Conversion Functions
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.
Path Expressions
The following is now possible for path expressions:
Access Control
The new addition WITH PRIVILEGED ACCESS switches
CDS access control off.
ORDER BY and UP TO, OFFSET in Subquery
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
Cardinality in LEFT OUTER JOIN
In a LEFT OUTER
JOIN, an addition ONE TO MANY can now be specified for the cardinality. This is evaluated as a note for optimization by
SAP HANA databases.
FOR ALL ENTRIES and Strings in the SELECT List
In the previous strict modes of the syntax check,
the addition FOR ALL ENTRIES
of statement SELECT could not be
specified together with columns of the types STRING and RAWSTRING or LCHR and LRAW in the
SELECT list. This restriction has been removed and now the syntax check simply issues a warning.
Strict Mode in the Syntax Check
If one the new features listed above is used in an Open SQL statement, the syntax check is performed in a
strict mode, which handles the statement more strictly than the regular syntax check.
Client Handling
The following (stricter) rules for the additions USING CLIENT and CLIENT SPECIFIED now apply when switching client handling in reads on CDS entities:
Replacement Service for Open SQL