Java Doc for TransactionManager.java in  » Database-DBMS » db-derby-10.2 » org » apache » derby » iapi » store » access » conglomerate » Java Source Code / Java DocumentationJava Source Code and Java Documentation

See Also:   TransactionController

Add to the list of post commit work that may be processed after this transaction commits.

Take whatever cleanup action is appropriate to a closed scan.

Take whatever cleanup action is appropriate to a closed conglomerateController.

Take whatever cleanup action is appropriate to a closed sortController.

Start an internal transaction.

Access methods often need direct access to the "Transaction" - ie.

Add to the list of post commit work that may be processed after this transaction commits. If this transaction aborts, then the post commit work list will be thrown away. No post commit work will be taken out on a rollback to save point.

This routine simply delegates the work to the Rawstore transaction.
Parameters:
  work - The post commit work to do.

Take whatever cleanup action is appropriate to a closed scan. It is likely this routine will remove references to the scan object that it was maintaining for cleanup purposes.

Take whatever cleanup action is appropriate to a closed conglomerateController. It is likely this routine will remove references to the ConglomerateController object that it was maintaining for cleanup purposes.

Take whatever cleanup action is appropriate to a closed sortController. It is likely this routine will remove references to the SortController object that it was maintaining for cleanup purposes.

The AccessFactory which started this transaction.

Start an internal transaction. An internal transaction is a completely separate transaction from the current user transaction. All work done in the internal transaction must be physical (ie. it can be undone physically by the rawstore at the page level, rather than logically undone like btree insert/delete operations). The rawstore guarantee's that in the case of a system failure all open Internal transactions are first undone in reverse order, and then other transactions are undone in reverse order.

Internal transactions are meant to implement operations which, if interupted before completion will cause logical operations like tree searches to fail. This special undo order insures that the state of the tree is restored to a consistent state before any logical undo operation which may need to search the tree is performed.

The new internal transaction.
exception:
  StandardException - Standard exception policy.

Access methods often need direct access to the "Transaction" - ie. the raw store transaction, so give access to it. The raw store transaction.
exception:
  StandardException - Standard exception policy.

The latched page in the conglomerate "congomid" is changing, do whatever is necessary to maintain the current position of all the scans open in this transaction.

For some conglomerates this may be a no-op.

Parameters:
  conglom - Conglomerate object of the conglomerate being changed.
Parameters:
  page - Page in the conglomerate being changed.
exception:
  StandardException - Standard exception policy.