ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  ABAP Database Access →  Native SQL →  ADBC - ABAP Database Connectivity →  ADBC - CL_SQL_CONNECTION 

ADBC - Database LUWs

For each open database connection that can be represented by an instance of class CL_SQL_CONNECTION, only one database LUW is active at any one time. When a connection is opened, the first database LUW of the connection is opened implicitly.

The class CL_SQL_CONNECTION contains the following instance methods:

• COMMIT

• ROLLBACK

These methods end the current database LUW of a connection using a database commit or database rollback. The current connection is set to inactive here. If the connection is still associated with an ADBC SQL statement and this statement is being used, it is activated again implicitly and a new database LUW opened at the same time.

The database LUWs of different connections are independent of one another and must be ended individually. When the work process is switched, with the resulting implicit database commit, this is executed on all open connections. The database commit on the default connection takes place last of all.

Other versions: 7.31 | 7.40 | 7.54

Notes

• Detailed information about database connections can be found here.

• To execute a database commit or a database rollback on the default connection using ADBC, an instance of class CL_SQL_CONNECTION must be created for this connection using CREATE OBJECT.

• Transaction control is possible only using the methods COMMIT and ROLLBACK of the class CL_SQL_CONNECTION, since only in this case are all actions required at the end of the transaction executed in the database interface. The native statements COMMIT or ROLLBACK should not be executed using CL_SQL_STATEMENT or CL_SQL_PREPARED_STATEMENT, to avoid critical side effects.