Help Center/ GaussDB(DWS)/ Standard Data Warehouse (8.1.3.x)/ Guide: JDBC- or ODBC-Based Development/ JDBC-Based Development/ Executing SQL Statements
Updated on 2023-10-31 GMT+08:00
View PDF

Executing SQL Statements

Executing an Ordinary SQL Statement

The application performs data (parameter statements do not need to be transferred) in the database by running SQL statements, and you need to perform the following steps:

  1. Create a statement object by triggering the createStatement method in Connection.

  2. Execute the SQL statement by triggering the executeUpdate method in Statement.

    If an execution request (not in a transaction block) received in the database contains multiple statements, the request is packed into a transaction. VACUUM is not supported in a transaction block. If one of the statements fails, the entire request will be rolled back.

  3. Close the statement object.

Executing a Prepared SQL Statement

Pre-compiled statements were once complied and optimized and can have additional parameters for different usage. For the statements have been pre-compiled, the execution efficiency is greatly improved. If you want to execute a statement for several times, use a precompiled statement. Perform the following procedure:

  1. Create a prepared statement object by calling the prepareStatement method in Connection.

  2. Set parameters by triggering the setShort method in PreparedStatement.

  3. Execute the precompiled SQL statement by triggering the executeUpdate method in PreparedStatement.

  4. Close the precompiled statement object by calling the close method in PreparedStatement.

Calling a Stored Procedure

Perform the following steps to call existing stored procedures through the JDBC interface in GaussDB(DWS):

  1. Create a call statement object by calling the prepareCall method in Connection.

  2. Set parameters by calling the setInt method in CallableStatement.

  3. Register with an output parameter by calling the registerOutParameter method in CallableStatement.

  4. Call the stored procedure by calling the execute method in CallableStatement.

  5. Obtain the output parameter by calling the getInt method in CallableStatement.

    For example:

  6. Close the call statement by calling the close method in CallableStatement.

    • Many database classes such as Connection, Statement, and ResultSet have a close() method. Close these classes after using their objects. Close these actions after using their objects. Closing Connection will close all the related Statements, and closing a Statement will close its ResultSet.
    • Some JDBC drivers support named parameters, which can be used to set parameters by name rather than sequence. If a parameter has a default value, you do not need to specify any parameter value but can use the default value directly. Even though the parameter sequence changes during a stored procedure, the application does not need to be modified. Currently, the GaussDB(DWS) JDBC driver does not support this method.
    • GaussDB(DWS) does not support functions containing OUT parameters, or default values of stored procedures and function parameters.

  • If JDBC is used to call a stored procedure whose returned value is a cursor, the returned cursor cannot be used.
  • A stored procedure and an SQL statement must be executed separately.

Batch Processing

When a prepared statement batch processes multiple pieces of similar data, the database creates only one execution plan. This improves the compilation and optimization efficiency. Perform the following procedure:

  1. Create a prepared statement object by calling the prepareStatement method in Connection.

  2. Call the setShort parameter for each piece of data, and call addBatch to confirm that the setting is complete.

  3. Execute batch processing by calling the executeBatch method in PreparedStatement.

  4. Close the precompiled statement object by calling the close method in PreparedStatement.

    Do not terminate a batch processing action when it is ongoing; otherwise, the database performance will deteriorate. Therefore, disable the automatic submission function during batch processing, and manually submit every several lines. The statement for disabling automatic submission is conn.setAutoCommit(false).

Parent topic: JDBC-Based Development