Get Example source ABAP code based on a different SAP table
ARTICLE • CL_SQL_PREPARED_STATEMENT ABAP_CLASS
CL_SQL_PREPARED_STATEMENT - Prepared SQL Statements 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 that must be passed to a syntactically correct SQL statement. 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.
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 stop 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.
