| Class and Description |
|---|
| com.mchange.v2.c3p0.DriverManagerDataSourceFactory
Use the new factories in
DataSources. See examples. |
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory
Use the new factories in
DataSources. See examples. |
| com.mchange.v2.c3p0.PoolConfig
as of c3p0-0.9.1. To manipulate config programmaticall, please use ComboPooledDataSource
|
| Method and Description |
|---|
| com.mchange.v2.c3p0.PooledDataSource.close(boolean)
the force_destroy argument is now meaningless, as pools are no longer
potentially shared between multiple DataSources.
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createReferenceable(DataSource, int, int, int, int, int, String)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createReferenceable(DataSource, String)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createReferenceable(String, String, String, String, int, int, int, int, int, String)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createReferenceable(String, String, String, String, String)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createSerializable(DataSource)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createSerializable(DataSource, int, int, int, int, int)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createSerializable(String, String, String, String)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.PoolBackedDataSourceFactory.createSerializable(String, String, String, String, int, int, int, int, int)
all implementations are now both Referenceable and Serializable.
use create()
|
| com.mchange.v2.c3p0.DataSources.forceDestroy(DataSource)
forceDestroy() is no longer meaningful, as a set of pools is now
directly associated with a DataSource, and not potentially shared.
(This simplification was made possible by canonicalization of
JNDI-looked-up DataSources within a virtual machine.) Just use
DataSources.destroy().
|
| com.mchange.v2.c3p0.PooledDataSource.getNumBusyConnections()
use getNumBusyConnectionsDefaultUser()
|
| com.mchange.v2.c3p0.PooledDataSource.getNumConnections()
use getNumConnectionsDefaultUser()
|
| com.mchange.v2.c3p0.PooledDataSource.getNumIdleConnections()
use getNumIdleConnectionsDefaultUser()
|
| com.mchange.v2.c3p0.PooledDataSource.getNumUnclosedOrphanedConnections()
use getNumUnclosedOrphanedConnectionsDefaultUser()
|
| com.mchange.v2.c3p0.PoolConfig.getTestConnectionOnCheckout()
use isTestConnectionOnCheckout
|
| com.mchange.v2.c3p0.DataSources.pooledDataSource(DataSource, PoolConfig)
if you want to set properties programmatically, please construct a ComboPooledDataSource and
set its properties rather than using PoolConfig
|