Home >> All >> org >> apache >> derby >> iapi >> store >> [ raw Javadoc ]

•	org.apache.derby.iapi.store.raw.data.* (2)	•	org.apache.derby.iapi.store.raw.log.* (4)
•	org.apache.derby.iapi.store.raw.xact.* (3)

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


Package Samples:

• org.apache.derby.iapi.store.raw.data
• org.apache.derby.iapi.store.raw.log
• org.apache.derby.iapi.store.raw.xact

Classes:

• ContainerHandle: A Container contains a contigious address space of pages, the pages start at page number Container.FIRST_PAGE_NUMBER and are numbered sequentially. The page size is set at addContainer() time. RESOLVE: this style of coding is not currently enforced If the caller calls getPage (or one of its variants) more than once on the same page, the caller must call unlatch a corresponding number of times in order to ensure that the page is latched. For example: Container c; Page p1 = c.getPage(Container.FIRST_PAGE_NUMBER); Page p2 = c.getPage(Container.FIRST_PAGE_NUMBER); p1.unlatch(); -- Page is still latched. ...
• Page: A Page contains an ordered set of records which are the stored form of rows. A record is a stream of bytes created from a row array. The record contains one or more fields, fields have a one to one correlation with the DataValueDescriptor's contained within a row array. A Page represents exclusive access to a data page within a container. Exclusive access is released by calling the unlatch() method, once that occurs the caller must no longer use the Page reference. Several of the methods in Page take a RecordHandle as an argument. RecordHandles are obtained from a Page, while holding exclusive ...
• RawStoreFactory: RawStoreFactory implements a single unit of transactional storage. A RawStoreFactory contains Segments and Segments contain Containers. Segments are identified by integer identifiers that are unique within a RawStoreFactory. Containers are also identified by unique integer identifiers within a RawStoreFactory, but will overlap with segment identifiers. LIMITS This is a list of (hopefully) all limits within the raw store. Where a size has more than one limit all are documented (rather than just the most restrictive) so that the correct limit can be found if the most restictive is every removed. ...
• LockingPolicy: Any object that implements this interface can be used as a locking policy for accessing a container. The locking policy must use the defined lock qualifiers (ContainerLock.CIS, RowLock.RS, etc.) and the standard lock manager. (A locking policy that just performs no locking wouldn't need to use these :-) A locking policy must use the object that is an instance of Transaction (originally obtained via startTransaction() in RawStoreFactory) as the compatibilitySpace for the LockFactory calls. A locking policy must use the passed in transaction as the compatability space and the lock group. This chain ...
• RawTransaction: RawTransaction is the form of Transaction used within the raw store. This allows the break down of RawStore functionality into (at least) three modules (Transactions, Data, Log) without exposing internal information on the external interface. The transaction will notify any Observer's just before the transaction is committed, aborted or a rollback to savepoint occurs. The argument passed to the update() method of the Observer's will be one of RawTransaction.COMMIT - transaction is committing RawTransaction.ABORT - transaction is aborting RawTransaction.SAVEPOINTROLLBACK - transaction is being rolled ...
• TransactionId: A transaction identifier that is only unique within a raw store, do not ever pass this out of raw store. During reboot, all transaction Ids that have ever generated a log record will not be reused. However, if you put away the transaction Id of a read only transaction, then the is no guarentee that the transactionId won't be reused when the system reboots. It is much safer to store away the ExternalTrasanctionId rather than the transactionId. The equals() method for TransactionId implements by value equality. MT - immutable
• LogicalUndoable: A LogicalUndoable is a log operation that operates on the content of a page and the log operation needs logical undo. This interface is used by LogicalUndo to extract information out of the log record, and to pass back to the logging system the real location where the roll back should happen. It has specific page information such as its segment Id, container Id, page number, and it knows how to restore a storable row from the information stored in the log record.
• FetchDescriptor: FetchDescriptor is used to package up all the arguments necessary to describe what rows and what row parts should be returned from the store back to language as part of a fetch. The FetchDescriptor may also contain scratch space used to process the qualifiers passed in the scan. This scratch space will be used to cache information about the qualifiers, valid column list, row size so that calculations need only be done once per scan rather than every iteration.
• Compensation: A Compensation operation can compensate for the action of a log operation. A Compensation operation itself is not undo-able, i.e., it is loggable but not undoable. A Compensation operation is generated by the logging system when it calls undoable.generateUndo(). GenerateUndo should be the only way a compensation operation can be made.
• TransactionFactory: This module is intended to be used only within the RawStore. RawStore functionality is accessed only through the RawStoreFactory interface. The transaction manager is responsible for: Generating unique transaction identifiers. Keeping a list of all open transactions within the raw store.
• RawContainerHandle: RawContainerHandle is the form of ContainerHandle that is used within the raw store. This allows the raw store to have a handle on dropped container without exposing this to the external interface, which is not allowed to get back a handle on a dropped container
• PageTimeStamp: The type definition of a time stamp that can be associated with pages that supports 'time stamp'. What a time stamp contains is up to the page. It is expected that a time stamp implementation will collaborate with the page to implement a value equality.
• RecordHandle: A handle to a record within a container. This interface does not provide an information about the data of the record, it is only used to perform updates, deletes and allow ordered record manipulation. MT - immutable
• Loggable: A Loggable is a record of a change of state or an event that happened in the RawStore in the context of a transaction. All changes in the RawStore must be logged. This is the root class for all log operations.
• RePreparable: An RePreparable operation is an operation that changed the state of the RawStore in the context of a transaction and the locks for this change can be reclaimed during recovery, following redo.
• D_ContainerKey: The D_BaseContainerHandle class provides diagnostic information about the BaseContainerHandle class. Currently this info is a single string of the form TABLE(conglomerate_id, container_id)
• GlobalTransactionId: A transaction identifier that is unique among all raw stores and all transactions The equals() method for TransactionId implements by value equality. MT - immutable
• ContainerLock: A ContainerLock represents a qualifier that is to be used when locking a container through a ContainerHandle. MT - Immutable
• Undoable: An Undoable operation is an operation that changed the state of the RawStore in the context of a transaction and this change can be rolled back.
• RowLock: A RowLock represents a qualifier that is to be used when locking a Row through a RecordHandle. MT - Immutable
• D_ContainerLock: The D_ContainerLock class provides diagnostic information about the ContainerLock qualifer, and is used for output in lock debugging.
• D_RowLock: The D_RowLock class provides diagnostic information about the RowLock qualifer, and is used for output in lock debugging.
• PageKey: A key that identifies a BasePage. Used as the key for the caching mechanism. MT - Immutable :
• ContainerKey: A key that identifies a Container within the RawStore. MT - Immutable
• AuxObject: The interface of objects which can be associated with a page while it's in cache.

Home | Contact Us | Privacy Policy | Terms of Service