The JDBC 3.0 specification added the maxStatements
ConnectionPooledDataSource
property to provide a standard mechanism for
enabling the pooling of PreparedStatements
and to specify the size of the statement
pool. However, there was no way for a driver to notify an external
statement pool when a PreparedStatement
becomes invalid. For some databases, a
statement becomes invalid if a DDL operation is performed that affects the
table. For example an application may create a temporary table to do some work
on the table and then destroy it. It may later recreate the same table when
it is needed again. Some databases will invalidate any prepared statements
that reference the temporary table when the table is dropped.
Similar to the methods defined in the ConnectionEventListener
interface,
the driver will call the StatementEventListener.statementErrorOccurred
method prior to throwing any exceptions when it detects a statement is invalid.
The driver will also call the StatementEventListener.statementClosed
method when a PreparedStatement
is closed.
Methods which allow a component to register a StatementEventListener with a
PooledConnection
have been added to the PooledConnection
interface.
Modifier and Type | Method and Description |
---|---|
public void | statementClosed(StatementEvent
an event object describing the source of
the event and that the event)PreparedStatement was closed.The driver calls this method on all |
public void | statementErrorOccurred(StatementEvent
an event object describing the source of the event,
the statement that is invalid and the exception the
driver is about to throw. The source of the event is
the event)PooledConnection which the invalid PreparedStatement
is associated with.The driver calls this method on all |
statementClosed | back to summary |
---|---|
public void statementClosed(StatementEvent event) The driver calls this method on all
|
statementErrorOccurred | back to summary |
---|---|
public void statementErrorOccurred(StatementEvent event) The driver calls this method on all
|