Home >> All >> org >> apache >> derby >> iapi >> store >> access >> [ conglomerate Javadoc ]

• org.apache.derby.iapi.store.access.conglomerate: Javadoc index of package org.apache.derby.iapi.store.access.conglomerate.


Package Samples:

• org.apache.derby.iapi.store.access.conglomerate

Classes:

• LogicalUndo: A Logical undo is an undo operation that operates on a different page from the page that has the original change. The reason one would need logical undo is when an uncommitted row move from one page to another in a nested internal transaction which is committed. For example, an uncommitted insert on a btree may be moved by a later split operation to another page, the split operation will have committed. If the insert needs to be rolled back, it can only be found at the new page where the split puts it and not at the original page where it is inserted. The logging and recovery system does not know ...
• Conglomerate: A conglomerate is an abstract storage structure (they correspond to access methods). The Conglomerate interface corresponds to a single instance of a conglomerate. In other words, for each conglomerate in the system, there will be one object implementing Conglomerate. The Conglomerate interface is implemented by each access method. The implementation must maintain enough information to properly open the conglomerate and scans, and to drop the conglomerate. This information typically will include the id of the container or containers in which the conglomerate is stored, and my also include property ...
• ScanManager: The ScanManager interface contains those methods private to access method implementors necessary to implement Scans on Conglomerates. Client of scans use the ScanController to interact with the scan.
• ScanControllerRowSource: A ScanControllerRowSource is both a RowSource and a ScanController. This interface is internal to Access for use in the case of RowSource which are implemented on top of a ScanController.
• TransactionManager: The TransactionManager interface provides methods on the transaction needed by an access method implementer, but should not be visible to clients of a TransactionController.
• MethodFactory: The interface of all access method factories. Specific method factories (sorts, conglomerates), extend this interface.
• Sort: The sort interface corresponds to an instance of an in-progress sort. Sorts are not persistent.
• ConglomerateFactory: The factory interface for all conglomerate access methods.
• SortFactory: The factory interface for all sort access methods.

Home | Contact Us | Privacy Policy | Terms of Service