SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Release-Specific Changes → Changes in Release 7.0, EhP2 →
Database Access in Release 7.0, EhP2
1. UPDATE for tables with strings
2. SAP buffering for single record accesses
3. Short strings as key fields of database tables
4. Maximum length of short strings in ABAP Dictionary
5. ABAP Database Connectivity (ADBC)
6. Streaming and locators in Open SQL
7. Specifying sorting columns in Open SQL
8. Overflow handling for sy-dbcnt
UPDATE for Tables with Strings
When the UPDATE statement is used
for a column of type STRING or RAWSTRING with the SET addition, you no longer need to specify the
primary key in full in the WHERE condition.
SAP Buffering for Single Record Accesses
Access to a table with single record buffering that an equality condition is set for in the WHERE clause for all key fields of the primary key uses
SAP buffering, even if
the SINGLE addition
is not specified for SELECT. Prior to Release 7.0 EhP2, SAP buffering was not used if SINGLE was missing.
Short Strings as Key Fields of Database Tables
From Release 7.0, EhP2, you can use short strings
as key fields of database tables. This can produce significant memory and performance gains in comparison with using long fields of type CHAR.
Maximum Length of Short Strings in ABAP Dictionary
The maximum length of short strings of type SSTRING has been increased from 255 to 1333.
ABAP Database Connectivity (ADBC)
The class-based framework ABAP Database Connectivity (ADBC), which has existed since Release 6.10 for dynamic access to the
Native SQL interface, is now also documented in the ABAP keyword documentation under
ADBC.
Streaming and Locators in Open SQL
From Release 7.0, EhP2, Open SQL supports processing of LOBs using data streams and locators.
Specifying Sorting Columns in Open SQL
The restriction that after ORDER BY
in SELECT only columns can be specified that are also specified after SELECT does not apply.
Overflow Handling for sy-dbcnt
If an overflow occurs in the system field sy-dbcnt, meaning the number of statements processed by SQL access is greater than 2,147,483,647, the value of sy-dbcnt is set to -1. The value was previously undefined.