My {@link #prepareStatement} methods, rather than creating a new {@link PreparedStatement}each time, may actually pull the {@link PreparedStatement} from a pool of unused statements.The {@link PreparedStatement#close} method of the returned {@link PreparedStatement} doesn'tactually close the statement, but rather returns it to my pool. (See {@link PoolablePreparedStatement}.) @see PoolablePreparedStatement @author Rodney Waldhoff (rwaldhof@us.britannica.com)
The {@link #prepareStatement} and {@link #prepareCall} methods, rather thancreating a new PreparedStatement each time, may actually pull the statement from a pool of unused statements. The {@link PreparedStatement#close} method of the returned statement doesn'tactually close the statement, but rather returns it to the pool. (See {@link PoolablePreparedStatement}, {@link PoolableCallableStatement}.) @see PoolablePreparedStatement @author Rodney Waldhoff @author Dirk Verbeeck @version $Revision: 1572244 $ $Date: 2014-02-26 20:38:08 +0000 (Wed, 26 Feb 2014) $ @since 2.0
The {@link #prepareStatement} and {@link #prepareCall} methods, rather than creating a new PreparedStatementeach time, may actually pull the statement from a pool of unused statements. The {@link PreparedStatement#close} method of the returned statement doesn'tactually close the statement, but rather returns it to the pool. (See {@link PoolablePreparedStatement}, {@link PoolableCallableStatement}.) @see PoolablePreparedStatement @author Rodney Waldhoff @author Dirk Verbeeck @version $Revision: 885261 $ $Date: 2009-11-29 15:07:02 -0500 (Sun, 29 Nov 2009) $
|
|
|
|
|
|