Get Example source ABAP code based on a different SAP table
• CL_SQL_PREPARED_STATEMENT ABAP_CLASS
ABAP_ADBC - CL_SQL_PREPARED_STATEMENT The class CL_SQL_PREPARED_STATEMENT is a subclass of CL_SQL_STATEMENT. It makes it possible to execute a SQL statement passed to it multiple times with different parameters. For this purpose, the instance constructor contains a mandatory input parameter STATEMENT of type string, to which a syntactically correct SQL statement must be passed. The SQL statement can contain placeholder ?, as is the case with the methods of CL_SQL_STATEMENT. Using the methods inherited from CL_SQL_STATEMENT, the placeholders can be linked to parameters and the instantiated SQL statement can be executed. In doing so, the SQL statement is not passed to the corresponding method. After the work process has been switched (see implicit database commit), a prepared statement can no longer be used. If a prepared statement is no longer needed, it should be closed using instance method close so that all resources that are needed in the database are released.
Latest notes:
Unlike in JDBC, the use of ? placeholders in ADBC is not restricted to prepared statements. In ADBC, the use of prepared statements is not a prerequisite for using placeholders to prevent SQL injections. Prepared statements are used only to improve performance in ADBC.
As with CL_SQL_STATEMENT, CL_SQL_PREPARED_STATEMENT should not be used to execute transaction control statements. ABAP_HINT_END
Example ABAP Coding
Insertion of multiple rows in a database table using a prepared statement in ADBC. The table is first emptied using AB_SQL and then read using AB_SQL . The values of the columns are determined by binding the components of temporary structures created using NEW to ? placeholders. ABEXA 00871 ABAP_EXAMPLE_END
