This topic describes how to use DBCP connection pool, OceanBase Connector/J, and OceanBase Cloud to build an application that performs basic database operations, such as creating tables, inserting, deleting, updating, and querying data.
Download the dbcp-oceanbase-client sample project Prerequisites
You have registered an Alibaba Cloud account and created an instance and an Oracle-compatible tenant. For more information, see Create an instance and Create a tenant.
You have obtained the connection string of the target Oracle-compatible tenant. For more information, see Obtain the connection string.
You have installed JDK 1.8 and Maven.
You have installed Eclipse.
Note
The code examples in this topic are run in Eclipse IDE for Java Developers 2022-03. You can also use any other tool that you prefer to run the code examples.
Procedure
Note
The following procedure describes how to compile and run the project in the Windows environment by using Eclipse IDE for Java Developers 2022-03. If you are using a different operating system or compiler, the procedure may vary.
Step 1: Import the dbcp-oceanbase-client project into Eclipse
Start Eclipse and choose File > Open Projects from File System.
In the dialog box that appears, click Directory to select the project directory and then click Finish.
Note
When you import a Maven project into Eclipse, it automatically detects the
pom.xmlfile in the project, downloads the required dependency libraries based on the described dependencies in the file, and adds them to the project.
View the project.

Step 2: Modify the database connection information in the dbcp-oceanbase-client project
Modify the database connection information in the dbcp-oceanbase-client/src/main/resources/db.properties file based on the connection string obtained from the prerequisites.
Here is an example:
...
url=jdbc:oceanbase://t5******.********.oceanbase.cloud:1521/test_user001
username=test_user001
password=******
...
- The connection address is
t5******.********.oceanbase.cloud. - The access port is 1521.
- The name of the database to be accessed is
test_user001. - The tenant connection account is
test_user. - The password is
******.
Step 3: Run the dbcp-oceanbase-client project
In the Project Explorer view, expand the src/main/java directory.
Right-click the Main.java file and choose Run As > Java Application.

View the project logs and output in the Eclipse console window.

You can also execute the following SQL statement in OceanBase Client (OBClient) to view the result.
obclient [SYS]> SELECT * FROM test_user001.test_tbl1;The return result is as follows:
+------+--------------+ | ID | NAME | +------+--------------+ | 5 | test_update | | 6 | test_insert6 | | 7 | test_insert7 | | 8 | test_insert8 | | 9 | test_insert9 | +------+--------------+ 5 rows in set
Project code introduction
Click dbcp-oceanbase-client to download the project code, which is a compressed file named dbcp-oceanbase-client.zip.
After decompressing the file, you will find a folder named dbcp-oceanbase-client. The directory structure is as follows:
dbcp-oceanbase-client
├── src
│ └── main
│ ├── java
│ │ └── com
│ │ └── example
│ │ └── Main.java
│ └── resources
│ └── db.properties
└── pom.xml
File description:
src: the root directory of the source code.main: the main code directory, containing the core logic of the application.java: the directory for Java source code.com: the directory for Java packages.example: the directory for packages of the sample project.Main.java: the main class file, containing logic for creating tables, inserting, deleting, updating, and querying data.resources: the directory for resource files, including configuration files.db.properties: the configuration file for the connection pool, containing relevant database connection parameters.pom.xml: the configuration file for the Maven project, used to manage project dependencies and build settings.
Introduction to the pom.xml file
The pom.xml file is a configuration file for Maven projects. It defines the project's dependencies, plugins, and build rules. Maven is a Java project management tool that can automatically download dependencies, compile, and package projects.
The pom.xml file in this topic includes the following main parts:
File declaration statement.
This statement declares the file to be an XML file using XML version
1.0and character encodingUTF-8.Sample code:
<?xml version="1.0" encoding="UTF-8"?>Configure the POM namespace and POM model version.
- Use
xmlnsto specify the POM namespace ashttp://maven.apache.org/POM/4.0.0. - Use
xmlns:xsito specify the XML namespace ashttp://www.w3.org/2001/XMLSchema-instance. - Use
xsi:schemaLocationto specify the POM namespace ashttp://maven.apache.org/POM/4.0.0and the location of the POM XSD file ashttp://maven.apache.org/xsd/maven-4.0.0.xsd. - Use
<modelVersion>to specify the POM model version used by the POM file as4.0.0.
Sample code:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <!-- Other configurations --> </project>- Use
Configure basic information.
- Use
<groupId>to specify the project's organization ascom.example. - Use
<artifactId>to specify the project's name asdbcp-oceanbase-client. - Use
<version>to specify the project's version as1.0-SNAPSHOT.
Sample code:
<groupId>com.example</groupId> <artifactId>dbcp-oceanbase-client</artifactId> <version>1.0-SNAPSHOT</version>- Use
Configure the properties of the project's source files.
Specify the Maven compiler plugin as
maven-compiler-pluginand set both the source code and target Java versions to 8. This means that the project's source code is written using Java 8 features, and the compiled bytecode will also be compatible with the Java 8 runtime environment. This setup ensures that the project can correctly handle Java 8 syntax and features during compilation and runtime.Note
Java 1.8 and Java 8 are different names for the same version.
Sample code:
<build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>8</source> <target>8</target> </configuration> </plugin> </plugins> </build>Configure the components that the project depends on.
Note
This part of the code defines the components that the project depends on as OceanBase Connector/J V2.4.2. For more information about other versions, see OceanBase JDBC driver.
Use
<dependency>to define the dependencies:oceanbase-client dependency:
- Use
<groupId>to specify the organization of the dependency ascom.oceanbase. - Use
<artifactId>to specify the name of the dependency asoceanbase-client. - Use
<version>to specify the version of the dependency as2.4.2.
- Use
dbcp dependency:
- Use
<groupId>to specify the organization of the dependency asorg.apache.commons. - Use
<artifactId>to specify the name of the dependency ascommons-dbcp2. - Use
<version>to specify the version of the dependency as2.9.0.
- Use
Sample code:
<dependencies> <dependency> <groupId>com.oceanbase</groupId> <artifactId>oceanbase-client</artifactId> <version>2.4.2</version> </dependency> <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-dbcp2</artifactId> <version>2.9.0</version> </dependency> </dependencies>
db.properties code introduction
db.properties is the connection pool configuration file in this example, which contains the configuration attributes of the connection pool. These attributes include the class name of the driver, database URL, username, password, size and limits of the connection pool, connection timeout, and options for handling abandoned connections.
The code in the db.properties file in this example mainly includes the following parts:
Configure the database connection parameters.
Set the class name of the driver. Here, it is the class name of the OceanBase JDBC driver,
com.oceanbase.jdbc.Driver.Configure the database connection URL, including the host IP, port number, and the schema to be accessed.
Configure the database username.
Configure the database password.
Sample code:
driverClassName=com.oceanbase.jdbc.Driver url=jdbc:oceanbase://$host:$port/$schema_name username=$user_name password=$passwordParameter description:
$host: the value of the-hparameter in the connection string, which is the connection address of OceanBase Cloud.$port: the value of the-Pparameter in the connection string, which is the connection port of OceanBase Cloud.$schema_name: the value of the-Dparameter in the connection string, which is the name of the database to be accessed.$user_name: the value of the-uparameter in the connection string, which is the account name.$password: the value of the-pparameter in the connection string, which is the account password.
Configure other parameters of the DBCP connection pool.
Set the initial size of the connection pool to
30, which is the number of connections to be created in the connection pool initially.Set the maximum number of connections in the connection pool to
30, which is the maximum number of connections allowed in the connection pool.Set the maximum number of connections that can be idle in the connection pool to
10.Set the minimum number of idle connections in the connection pool to
5. If the number of idle connections is less than this value, the connection pool will create new connections.Set the maximum wait time (in milliseconds) for obtaining a connection from the connection pool to
1000. If all connections in the connection pool are occupied and there are no available connections, the operation to obtain a connection will wait until an available connection is available or the maximum wait time is exceeded.Set the timeout (in seconds) before abandoned connections are removed to
1.Note
The default value of
removeAbandonedTimeoutis 300 seconds. In this example, it is set to 1 second for testing purposes. You can adjust this value as needed to meet the requirements of your application.Configure whether the connection pool recycles connections that are no longer used in the program:
- Set whether to detect and remove abandoned connections during maintenance to
true. - Set whether to detect and remove abandoned connections when borrowing a connection from the connection pool to
true.
- Set whether to detect and remove abandoned connections during maintenance to
Sample code:
initialSize=30 maxTotal=30 maxIdle=10 minIdle=5 maxWaitMillis=1000 removeAbandonedTimeout=1 removeAbandonedOnMaintenance=true removeAbandonedOnBorrow=true
Notice
The specific configuration of parameters depends on the project requirements and the characteristics of the database. We recommend that you adjust and configure the parameters as needed. For more information about the DBCP connection pool parameters, see BasicDataSource Configuration Parameters.
Basic data source configuration parameters of the DBCP connection pool:
| Category | Parameter | Default value | Description |
|---|---|---|---|
| Required parameters | driverClass | N/A | Specifies the class name of the database driver. |
| url | N/A | Specifies the URL used to connect to the database. | |
| username | N/A | Specifies the username used to connect to the database. | |
| password | N/A | Specifies the password used to connect to the database. | |
| Recommended parameters | initialSize | 0 | Specifies the initial size of the connection pool, that is, the number of initial connections created when the connection pool is started. If this parameter is set to a value greater than 0, the specified number of connections will be created during the initialization of the connection pool. This can help create connections in advance and reduce the latency when the client first requests a connection. |
| maxTotal | 8 | Specifies the maximum number of connections allowed in the connection pool. If this parameter is set to a negative value, there is no limit. | |
| maxIdle | 8 | Specifies the maximum number of idle connections allowed in the connection pool without releasing additional connections. If this parameter is set to a negative value, there is no limit. | |
| minIdle | 0 | Specifies the minimum number of idle connections allowed in the connection pool without releasing additional connections. If this parameter is set to a negative value, there is no limit. | |
| maxWaitMillis | indefinitely | Specifies the maximum waiting time (in milliseconds) for obtaining a connection from the connection pool. If this parameter is set to -1, the connection pool will wait indefinitely. If this parameter is set to a positive value, when all connections in the connection pool are occupied, the operation to obtain a connection will wait for the specified time. If the time limit is exceeded, an exception will be thrown. | |
| validationQuery | N/A | Specifies the SQL query statement used to validate the connection. If specified, this query must be a SQL SELECT statement that returns at least one row. If not specified, the connection will be validated by calling the isValid() method. |
|
| testOnBorrow | true | Specifies whether to validate the connection when borrowing an object from the connection pool. If the object cannot be validated, it will be removed from the connection pool, and another object will be tried to be borrowed. | |
| testWhileIdle | false | Specifies whether to validate the connection when it is idle. If this parameter is set to true, the connection pool will periodically execute the validation query to check the validity of idle connections. If the object fails the validation, it will be removed from the connection pool. |
|
| Optional parameters | connectionProperties | N/A | Specifies additional connection properties in key-value pairs, which will be passed to the underlying JDBC driver when obtaining a database connection. The string format must be propertyName=property;
NoticeThe |
|
false | These parameters control the behavior of removing connections that are considered abandoned.
true, the connection pool can automatically detect and remove abandoned connections. Abandoned connections are those that have been unused for a long time, which may be due to the application not properly closing the connection. By removing these abandoned connections, database resources can be released, and the performance and efficiency of the connection pool can be improved. |
Introduction to Main.java
The Main.java file is part of the sample program, demonstrating how to obtain a database connection through a DBCP connection pool and perform a series of database operations, including creating tables, inserting data, deleting data, updating data, querying data, and printing the query results.
The code in the Main.java file of this topic mainly includes the following parts:
Import the required classes and interfaces.
Import the required classes and interfaces, including those for reading files, performing database operations, and managing the database connection pool. These classes and interfaces will be used in the subsequent code.
- Declare a package named
com.exampleto store the current Java class. - Import the
java.io.FileInputStreamclass to read files. - Import the
java.sql.Connectioninterface to represent a database connection. - Import the
java.sql.PreparedStatementinterface to represent a precompiled SQL statement. - Import the
java.sql.ResultSetinterface to represent a result set from a database query. - Import the
java.sql.SQLExceptionexception class to represent SQL operation exceptions. - Import the
java.util.Propertiesclass to load configuration files. - Import the
org.apache.commons.dbcp2.BasicDataSourceclass to represent a database connection pool. - Import the
org.apache.commons.dbcp2.BasicDataSourceFactoryclass to create a database connection pool.
Code:
package com.example; import java.io.FileInputStream; import java.sql.Connection; import java.sql.PreparedStatement; import java.sql.ResultSet; import java.sql.SQLException; import java.util.Properties; import org.apache.commons.dbcp2.BasicDataSource; import org.apache.commons.dbcp2.BasicDataSourceFactory;- Declare a package named
Define the class name and methods.
- Create the Main class and define a
mainmethod as the entry point of the program. - In the
mainmethod, first call thecreateDataSource()method to create a connection pool objectdataSource. - Use the
try-with-resourcesstatement to automatically close resources when the lifecycle of the connection pool object ends. - In the
trycode block, call thegetConnection()method to obtain a database connection objectconnfrom the connection pool. - Successively call the
createTable(),insertData(),deleteData(),updateData(), andqueryData()methods to execute the corresponding database operations. - In the event of an exception, print the exception information using the
catchblock.
Code:
public class Main { public static void main(String[] args) { try (BasicDataSource dataSource = createDataSource()) { try (Connection conn = dataSource.getConnection()) { createTable(conn); insertData(conn); deleteData(conn); updateData(conn); queryData(conn); } } catch (Exception e) { e.printStackTrace(); } } // Create a connection pool. // Define a method for creating tables. // Define a method for inserting data. // Define a method for deleting data. // Define a method for updating data. // Define a method for querying data. }- Create the Main class and define a
Create a connection pool.
Provide a convenient method for creating a database connection pool, initializing the connection pool object by reading parameters from the configuration file. The specific steps are as follows:
- Define a private static method
createDataSource()that returns aBasicDataSourceobject. The method may throw anExceptionexception. - Create a
Propertiesobjectpropsto store the database connection configuration information. - Create a
FileInputStreamobjectisto read thedb.propertiesfile located in thesrc/main/resourcesdirectory. - Use the
load()method to load the key-value pairs from thedb.propertiesfile into thepropsobject. - Call the
BasicDataSourceFactory.createDataSource(props)method to create and return aBasicDataSourceobject using thepropsobject as the parameter.
Code:
private static BasicDataSource createDataSource() throws Exception { Properties props = new Properties(); FileInputStream is = new FileInputStream("src/main/resources/db.properties"); props.load(is); return BasicDataSourceFactory.createDataSource(props); }- Define a private static method
Define a method for creating tables.
Provide a method for creating a specified table in the database. It accepts a connection object as a parameter and executes a create-table SQL statement using a precompiled approach. The specific steps are as follows:
- Define a private static method
createTable()that accepts aConnectionobject as a parameter. The method may throw anSQLExceptionexception. - Define a string variable
createTableSqlto store the SQL statement for creating a table. The SQL statement specifies the table name astest_tbl1and defines two columns: one is aNUMBERtype column namedid, and the other is aVARCHAR2(32)type column namedname. - Use the
conn.prepareStatement(createTableSql)method to create aPreparedStatementobjectcreateTableStmtfor executing precompiled SQL statements. - Call the
execute()method to execute the SQL statement for creating the table.
Code:
private static void createTable(Connection conn) throws SQLException { String createTableSql = "CREATE TABLE test_tbl1 (id NUMBER, name VARCHAR2(32))"; try (PreparedStatement createTableStmt = conn.prepareStatement(createTableSql)) { createTableStmt.execute(); } }- Define a private static method
Define a method for inserting data.
Provide a method for inserting specified data into a table in the database. It accepts a connection object as a parameter and executes an insert-data SQL statement using a precompiled approach. The specific steps are as follows:
Define a private static method
insertData()that accepts aConnectionobject as a parameter. The method may throw anSQLExceptionexception.Define a string variable
insertDataSqlto store the SQL statement for inserting data.Use the
conn.prepareStatement(insertDataSql)method to create aPreparedStatementobjectinsertDataStmtfor executing precompiled SQL statements.Use a
forloop to insert data into the table:- Loop 10 times, inserting one piece of data in each iteration.
- Use the
setInt()method to set the value of the loop variableias the first parameter value in the SQL statement. - Use the
setString()method to set the stringtest_insert + ias the second parameter value in the SQL statement. - Call the
executeUpdate()method to execute the SQL statement for inserting data into the database.
Code:
private static void insertData(Connection conn) throws SQLException { String insertDataSql = "INSERT INTO test_tbl1 (id, name) VALUES (?, ?)"; try (PreparedStatement insertDataStmt = conn.prepareStatement(insertDataSql)) { for (int i = 0; i < 10; i++) { insertDataStmt.setInt(1, i); insertDataStmt.setString(2, "test_insert" + i); insertDataStmt.executeUpdate(); } } }Define a method for deleting data.
Provide a method for deleting data from the database that meets specific conditions. It accepts a connection object as a parameter and executes the SQL statement for deleting data using a precompiled statement. The steps are as follows:
- Define a private static method
deleteData()that accepts aConnectionobject as a parameter and may throw anSQLException. - Define a string variable
deleteDataSqlto store the SQL statement for deleting data. - Use the
conn.prepareStatement(deleteDataSql)method to create aPreparedStatementobjectdeleteDataStmtfor executing the precompiled SQL statement. - Use the
setInt()method to set the number 5 as the parameter value in the SQL statement. - Call the
executeUpdate()method to execute the SQL statement and delete data that meets the specified conditions from the database.
Code:
private static void deleteData(Connection conn) throws SQLException { String deleteDataSql = "DELETE FROM test_tbl1 WHERE id < ?"; try (PreparedStatement deleteDataStmt = conn.prepareStatement(deleteDataSql)) { deleteDataStmt.setInt(1, 5); deleteDataStmt.executeUpdate(); } }- Define a private static method
Define a method for updating data.
Provide a method for updating data in the database that meets specific conditions. It accepts a connection object as a parameter and executes the SQL statement for updating data using a precompiled statement. The steps are as follows:
- Define a private static method
updateData()that accepts aConnectionobject as a parameter and may throw anSQLException. - Define a string variable
updateDataSqlto store the SQL statement for updating data. - Use the
conn.prepareStatement(updateDataSql)method to create aPreparedStatementobjectupdateDataStmtfor executing the precompiled SQL statement. - Use the
setString()method to set the stringtest_updateas the first parameter value in the SQL statement. - Use the
setInt()method to set the number5as the second parameter value in the SQL statement. - Call the
executeUpdate()method to execute the SQL statement and update data that meets the specified conditions in the database.
Code:
private static void updateData(Connection conn) throws SQLException { String updateDataSql = "UPDATE test_tbl1 SET name = ? WHERE id = ?"; try (PreparedStatement updateDataStmt = conn.prepareStatement(updateDataSql)) { updateDataStmt.setString(1, "test_update"); updateDataStmt.setInt(2, 5); updateDataStmt.executeUpdate(); } }- Define a private static method
Define a method for querying data.
Provide a method for querying data from the database and processing it. It accepts a connection object as a parameter and executes the SQL statement for querying data using a precompiled statement. The steps are as follows:
Define a private static method
queryData()that accepts aConnectionobject as a parameter and may throw anSQLException.Define a string variable
queryDataSqlto store the SQL statement for querying data.Use the
conn.prepareStatement(queryDataSql)method to create aPreparedStatementobjectqueryDataStmtfor executing the precompiled SQL statement.Execute the SQL query using the
queryDataStmt.executeQuery()method and use theResultSetobjectrsto receive the query results.Use a
whileloop to traverse the query result set by calling thers.next()method:- Use the
getInt()method to get the integer value of the column namedidin the result set and assign it to the variableid. - Use the
getString()method to get the string value of the column namednamein the result set and assign it to the variablename. - Print the
idandnameof the query results.
- Use the
Code:
private static void queryData(Connection conn) throws SQLException { String queryDataSql = "SELECT * FROM test_tbl1"; try (PreparedStatement queryDataStmt = conn.prepareStatement(queryDataSql)) { try (ResultSet rs = queryDataStmt.executeQuery()) { while (rs.next()) { int id = rs.getInt("id"); String name = rs.getString("name"); System.out.println("id: " + id + ", name: " + name); } } } }
Full code
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>dbcp-oceanbase-client</artifactId>
<version>1.0-SNAPSHOT</version>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>8</source>
<target>8</target>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>com.oceanbase</groupId>
<artifactId>oceanbase-client</artifactId>
<version>2.4.2</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-dbcp2</artifactId>
<version>2.9.0</version>
</dependency>
</dependencies>
</project>
# Database Connect Information
driverClassName=com.oceanbase.jdbc.Driver
url=jdbc:oceanbase://$host:$port/$schema_name
username=$user_name
password=$password
# ConnectionPool Parameters
initialSize=30
maxTotal=30
maxIdle=10
minIdle=5
maxWaitMillis=1000
removeAbandonedTimeout=1
removeAbandonedOnMaintenance=true
removeAbandonedOnBorrow=true
package com.example;
import java.io.FileInputStream;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Properties;
import org.apache.commons.dbcp2.BasicDataSource;
import org.apache.commons.dbcp2.BasicDataSourceFactory;
public class Main {
public static void main(String[] args) {
try (BasicDataSource dataSource = createDataSource()) {
try (Connection conn = dataSource.getConnection()) {
createTable(conn);
insertData(conn);
deleteData(conn);
updateData(conn);
queryData(conn);
}
} catch (Exception e) {
e.printStackTrace();
}
}
// Create ConnectionPool
private static BasicDataSource createDataSource() throws Exception {
Properties props = new Properties();
FileInputStream is = new FileInputStream("src/main/resources/db.properties");
props.load(is);
return BasicDataSourceFactory.createDataSource(props);
}
// Create table
private static void createTable(Connection conn) throws SQLException {
String createTableSql = "CREATE TABLE test_tbl1 (id NUMBER, name VARCHAR2(32))";
try (PreparedStatement createTableStmt = conn.prepareStatement(createTableSql)) {
createTableStmt.execute();
}
}
// Insert data
private static void insertData(Connection conn) throws SQLException {
String insertDataSql = "INSERT INTO test_tbl1 (id, name) VALUES (?, ?)";
try (PreparedStatement insertDataStmt = conn.prepareStatement(insertDataSql)) {
for (int i = 0; i < 10; i++) {
insertDataStmt.setInt(1, i);
insertDataStmt.setString(2, "test_insert" + i);
insertDataStmt.executeUpdate();
}
}
}
// Delete data
private static void deleteData(Connection conn) throws SQLException {
String deleteDataSql = "DELETE FROM test_tbl1 WHERE id < ?";
try (PreparedStatement deleteDataStmt = conn.prepareStatement(deleteDataSql)) {
deleteDataStmt.setInt(1, 5);
deleteDataStmt.executeUpdate();
}
}
// Update data
private static void updateData(Connection conn) throws SQLException {
String updateDataSql = "UPDATE test_tbl1 SET name = ? WHERE id = ?";
try (PreparedStatement updateDataStmt = conn.prepareStatement(updateDataSql)) {
updateDataStmt.setString(1, "test_update");
updateDataStmt.setInt(2, 5);
updateDataStmt.executeUpdate();
}
}
// Query data
private static void queryData(Connection conn) throws SQLException {
String queryDataSql = "SELECT * FROM test_tbl1";
try (PreparedStatement queryDataStmt = conn.prepareStatement(queryDataSql)) {
try (ResultSet rs = queryDataStmt.executeQuery()) {
while (rs.next()) {
int id = rs.getInt("id");
String name = rs.getString("name");
System.out.println("id: " + id + ", name: " + name);
}
}
}
}
}
References
For more information about OceanBase Connector/J, see OceanBase JDBC driver.