A) Connection pooling is a technique of creating and managing a pool of connections that are ready for use by any thread that needs them.

This technique of “pooling” connections is based on the fact that most applications only need a thread to have access to a JDBC connection when they are actively processing a transaction, which usually take only milliseconds to complete. When not processing a transaction, the connection would otherwise sit idle. Instead, connection pooling allows the idle connection to be used by some other thread to do useful work.

In practice, when a thread needs to do work against a MySQL or other database with JDBC, it requests a connection from the pool. When the thread is finished using the connection, it returns it to the pool, so that it may be used by any other threads that want to use it.

When the connection is “loaned out” from the pool, it is used exclusively by the thread that requested it. From a programming point of view, it is the same as if your thread called DriverManager.getConnection() every time it needed a JDBC connection, however with connection pooling, your thread may end up using either a new, or already-existing connection.

Random Posts

When stmt.executeUpdate is called, the JDBC Driver sends the SQL Statement(create—) to the database server. The database server parses and execute the SQL statement

Note: Any Business application uses the Database servers to perform the following 4 operations(getting the data for available in the database is called as Reading the data)

CURD is nothing but

C :- Create (insert—->statement)

U :- Update (update—–>statement)

R :- Read (select——->statement)

D :- Delete (delete——>statement)

for Ex: we can provide the code as shown below to perform create operation

Statement stmt=con.createStatement();

String Vsql=”insert into student values(200,’ram’,22,’ampet’);

stmt.executeUpdate(Vsql);

Random Posts