public interface TransactionalWriter extends RowSetWriter
SyncProvider
abstract class so that it has finer grained
transaction control.
If one or more disconnected RowSet
objects are participating
in a global transaction, they may wish to coordinate their synchronization
commits to preserve data integrity and reduce the number of
synchronization exceptions. If this is the case, an application should set
the CachedRowSet
constant COMMIT_ON_ACCEPT_CHANGES
to false
and use the commit
and rollback
methods defined in this interface to manage transaction boundaries.
Modifier and Type | Method and Description |
---|---|
void |
commit()
Makes permanent all changes that have been performed by the
acceptChanges method since the last call to either the
commit or rollback methods. |
void |
rollback()
Undoes all changes made in the current transaction.
|
void |
rollback(Savepoint s)
Undoes all changes made in the current transaction made prior to the given
Savepoint object. |
writeData
void commit() throws SQLException
acceptChanges
method since the last call to either the
commit
or rollback
methods.
This method should be used only when auto-commit mode has been disabled.SQLException
- if a database access error occurs or the
Connection
object within this CachedRowSet
object is in auto-commit modevoid rollback() throws SQLException
SQLException
- if a database access error occurs or the Connection
object within this CachedRowSet
object is in auto-commit modevoid rollback(Savepoint s) throws SQLException
Savepoint
object. This method should be used only when auto-commit
mode has been disabled.s
- a Savepoint
object marking a savepoint in the current
transaction. All changes made before s was set will be undone.
All changes made after s was set will be made permanent.SQLException
- if a database access error occurs or the Connection
object within this CachedRowSet
object is in auto-commit mode Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.