com.mchange.v2.c3p0.util

public Class CloseReportingConnectionWrapper

Class Inheritance

extends FilterConnection

java.lang.Object
com.mchange.v2.sql.filter.FilterConnection
com.mchange.v2.c3p0.util.CloseReportingConnectionWrapper

Imports

java.sql.*, com.mchange.v2.sql.filter.*

Deprecated

Please use com.mchange.v2.c3p0.debug.CloseLoggingConnectionWrapper

Field Summary

Inherited from com.mchange.v2.sql.filter.FilterConnection:: inner

Constructor Summary

Access	Constructor and Description
public	CloseReportingConnectionWrapper(Connection conn)

Method Summary

Modifier and Type	Method and Description
public void	close() Overrides com.mchange.v2.sql.filter.FilterConnection.close. Implements java.sql.Connection.close. Releases this `Connection` object's database and JDBC resources immediately instead of waiting for them to be automatically released.

Constructor Detail

CloseReportingConnectionWrapper	back to summary
public CloseReportingConnectionWrapper(Connection conn)

Method Detail

close back to summary

close	back to summary
public void close() throws SQLException Overrides com.mchange.v2.sql.filter.FilterConnection.close. Implements java.sql.Connection.close. Doc from java.sql.Connection.close. Releases this `Connection` object's database and JDBC resources immediately instead of waiting for them to be automatically released. Calling the method `close` on a `Connection` object that is already closed is a no-op. It is strongly recommended that an application explicitly commits or rolls back an active transaction prior to calling the `close` method. If the `close` method is called and there is an active transaction, the results are implementation-defined. Exceptions SQLException: if a database access error occurs

public void close() throws SQLException

Overrides com.mchange.v2.sql.filter.FilterConnection.close.

Implements java.sql.Connection.close.

Doc from java.sql.Connection.close.

Releases this Connection object's database and JDBC resources immediately instead of waiting for them to be automatically released.

Calling the method close on a Connection object that is already closed is a no-op.

It is strongly recommended that an application explicitly commits or rolls back an active transaction prior to calling the close method. If the close method is called and there is an active transaction, the results are implementation-defined.

Exceptions

SQLException:: if a database access error occurs