| java.lang.Object
 org.apache.derbyTesting.functionTests.util.corruptio.CorruptBaseStorageFactory
All known Subclasses: org.apache.derbyTesting.functionTests.util.corruptio.CorruptDiskStorageFactory,
| CorruptBaseStorageFactory | | abstract class CorruptBaseStorageFactory implements WritableStorageFactory(Code) | | This class provides a proxy base implementation of the
WritableStorageFactory interface to instrument I/O operations for testing
purposes.
Some methods in this class adds support for corrupting the I/O operation
sent by the engine before invoking the real storage factory underneath.
By deault all the calls will go to the real storage factory defined by the
concrete class, unless corruption is enabled through CorruptibleIo instance.
See Also: CorruptibleIo
See Also: WritableStorageFactory
See Also: StorageFactory |
| CorruptBaseStorageFactory | | CorruptBaseStorageFactory()(Code) | | Most of the initialization is done in the init method.
|
| getCanonicalName | | public String getCanonicalName() throws IOException(Code) | | Get the canonical name of the database.
This is a name that uniquely identifies it. It is system dependent.
The normal, disk based implementation uses method
java.io.File.getCanonicalPath on the directory holding the
database to construct the canonical name.
the canonical name
exception:
IOException - if an IO error occurred during the construction of the name. |
| getSeparator | | public char getSeparator()(Code) | | Get the pathname separator character used by the StorageFile
implementation.
the pathname separator character. (Normally '/' or '\'). |
| getStorageFactoryVersion | | public int getStorageFactoryVersion()(Code) | | |
| getTempDir | | public StorageFile getTempDir()(Code) | | Get the abstract name of the directory that holds temporary files.
a directory name |
| init | | public void init(String home, String databaseName, String tempDirName, String uniqueName) throws IOException(Code) | | Classes implementing the StorageFactory interface must have a null
constructor. This method is called when the database is booted up to
initialize the class. It should perform all actions necessary to start
the basic storage, such as creating a temporary file directory.
The init method will be called once, before any other method is called,
and will not be called again.
Parameters:
home - The name of the directory containing the database. It comes from the system.home system property.It may be null. A storage factory may decide to ignore this parameter. (For instance the classpathstorage factory ignores it.)
Parameters:
databaseName - The name of the database (directory). All relative pathnames are relative to this directory.If null then the storage factory will only be used to deal with the directory containing the databases.
Parameters:
create - If true then the database is being created.
Parameters:
tempDirName - The name of the temporary file directory set in properties. If null then a default directory shouldbe used. Each database should get a separate temporary file directory within this one to avoid collisions.
Parameters:
uniqueName - A unique name that can be used to create the temporary file directory for this database.
exception:
IOException - on an error (unexpected). |
| isFast | | public boolean isFast()(Code) | | This method is used to determine whether the storage is fast
(RAM based) or slow (disk based).
It may be used by the database engine to determine the default size of
the page cache.
true if the storage is fast, false if it is slow. |
| isReadOnlyDatabase | | public boolean isReadOnlyDatabase()(Code) | | |
| newStorageFile | | public StorageFile newStorageFile(String path)(Code) | | Construct a StorageFile from a path name.
Parameters:
path - The path name of the file A corresponding StorageFile object |
| newStorageFile | | public StorageFile newStorageFile(String directoryName, String fileName)(Code) | | Construct a StorageFile from a directory and file name.
Parameters:
directoryName - The directory part of the path name.
Parameters:
fileName - The name of the file within the directory. A corresponding StorageFile object |
| newStorageFile | | public StorageFile newStorageFile(StorageFile directoryName, String fileName)(Code) | | Construct a StorageFile from a directory and file name.
Parameters:
directoryName - The directory part of the path name.
Parameters:
fileName - The name of the file within the directory. A corresponding StorageFile object |
| shutdown | | public void shutdown()(Code) | | |
| supportsRandomAccess | | public boolean supportsRandomAccess()(Code) | | Determine whether the storage supports random access.
If random access is not supported then it will only be accessed using
InputStreams and OutputStreams (if the database is writable).
true if the storage supports random access, false if it is writable. |
| supportsRws | | public boolean supportsRws()(Code) | | This method tests whether the "rws" and "rwd" modes are implemented.
If the "rws" method is supported then the database engine will conclude
that the write methods of "rws" mode StorageRandomAccessFiles are
slow but the sync method is fast and optimize accordingly.
true if an StIRandomAccess file opened with "rws" or "rwd" modes immediately writes data to theunderlying storage, false if not. |
| sync | | public void sync(OutputStream stream, boolean metaData) throws IOException, SyncFailedException(Code) | | Force the data of an output stream out to the underlying storage.
That is, ensure that it has been made persistent. If the database is to
be transient, that is, if the database does not survive a restart, then
the sync method implementation need not do anything.
Parameters:
stream - The stream to be synchronized.
Parameters:
metaData - If true then this method must force both changes to thefile's contents and metadata to be written to storage; if false, it need only force file content changes to bewritten. The implementation is allowed to ignore this parameter and always force out metadata changes.
exception:
IOException - if an I/O error occurs.
exception:
SyncFailedException - Thrown when the buffers cannot be flushed,or because the system cannot guarantee that all the buffers have been synchronized with physical media. |
|
|