| java.lang.Object org.apache.derby.impl.store.access.heap.HeapConglomerateFactory
HeapConglomerateFactory | public HeapConglomerateFactory()(Code) | | |
getConglomerateFactoryId | public int getConglomerateFactoryId()(Code) | | Return the conglomerate factory id.
Return a number in the range of 0-15 which identifies this factory.
Code which names conglomerates depends on this range currently, but
could be easily changed to handle larger ranges. One hex digit seemed
reasonable for the number of conglomerate types being currently
considered (heap, btree, gist, gist btree, gist rtree, hash, others? ).
See Also: ConglomerateFactory.getConglomerateFactoryId an unique identifier used to the factory into the conglomid. |
primaryFormat | public UUID primaryFormat()(Code) | | Return the primary format that this access method supports.
The heap currently only supports one format, HEAPFORMAT1.
See Also: MethodFactory.primaryFormat |
readConglomerate | public Conglomerate readConglomerate(TransactionManager xact_mgr, ContainerKey container_key) throws StandardException(Code) | | Return Conglomerate object for conglomerate with container_key.
Return the Conglomerate Object. This is implementation specific.
Examples of what will be done is using the key to find the file where
the conglomerate is located, and then executing implementation specific
code to instantiate an object from reading a "special" row from a
known location in the file. In the btree case the btree conglomerate
is stored as a column in the control row on the root page.
This operation is costly so it is likely an implementation using this
will cache the conglomerate row in memory so that subsequent accesses
need not perform this operation.
Parameters: xact_mgr - transaction to perform the create in. Parameters: container_key - The unique id of the existing conglomerate. An instance of the conglomerate. exception: StandardException - Standard exception policy. |
supportsFormat | public boolean supportsFormat(UUID formatid)(Code) | | Return whether this access method supports the format supplied in
the argument.
The heap currently only supports one format, HEAPFORMAT1.
See Also: MethodFactory.supportsFormat |
supportsImplementation | public boolean supportsImplementation(String implementationId)(Code) | | Return whether this access method implements the implementation
type given in the argument string.
The heap only has one implementation type, "heap".
See Also: MethodFactory.supportsImplementation |
|
|