Create an incremental storage manager with the given name. The bucket size has to be given in bytes and the cache size in buckets. The bucket size is checked or calculated as described in IncrementalStMan.h.
Create an incremental storage manager with the given name. The specifications are in the record (as created by dataManagerSpec).
Clone this object. It does not clone ISMColumn objects possibly used. The caller has to delete the newly created object.
Get the type name of the data manager (i.e. IncrementalStMan).
Get the name given to the storage manager (in the constructor).
Record a record containing data manager specifications.
Get the version of the class.
Set the cache size (in buckets).
Get the current cache size (in buckets).
Clear the cache used by this storage manager. It will flush the cache as needed and remove all buckets from it.
Show the statistics of all caches used.
Get the bucket size (in bytes).
Get the size of a uInt in external format (can be canonical or local).
Get the bucket containing the given row. Also return the first and last row of that bucket. The bucket object is created and deleted by the caching mechanism.
Get the next bucket. cursor=0 indicates the start of the iteration. The first bucket returned is the bucket containing the rownr given in bucketStartRow. After each iteration BucketStartRow and bucketNrrow are set. A 0 is returned when no more buckets. The bucket object is created and deleted by the caching mechanism.
Get access to the temporary buffer.
Get a unique column number for the column (it is only unique for this storage manager). This is used by ISMColumnIndArr to create a unique file name.
Get the number of rows in this storage manager.
Can the storage manager add rows? (yes)
Can the storage manager delete rows? (yes)
Can the storage manager add columns? (not yet)
Can the storage manager delete columns? (not yet)
Make the object from the type name string. This function gets registered in the DataManager "constructor" map. The caller has to delete the object.
Get access to the given column.
Add a bucket to the storage manager (i.e. to the cache). The pointer is taken over.
Make the current bucket in the cache dirty (i.e. something has been changed in it and it needs to be written when removed from the cache). (used by ISMColumn::putValue).
Open (if needed) the file for indirect arrays with the given mode. Return a pointer to the object.
Assignment cannot be used.
(Re)create the index, file, and cache object.
Flush and optionally fsync the data. It returns a True status if it had to flush (i.e. if data have changed).
Let the storage manager create files as needed for a new table. This allows a column with an indirect array to create its file.
Open the storage manager file for an existing table, read in the data, and let the ISMColumn objects read their data.
Resync the storage manager with the new file contents. This is done by clearing the cache.
Reopen the storage manager files for read/write.
The data manager will be deleted (because all its columns are requested to be deleted). So clean up the things needed (e.g. delete files).
Let the storage manager initialize itself. It is used by create and open.
Add rows to the storage manager. Per column it extends the interval for which the last value written is valid.
Delete a row from all columns.
Do the final addition of a column. The DataManagerColumn object has already been created (by the makeXXColumn function) and added to colSet_p. However, it still has to be added to the data files, which is done by this function. It uses the pointer to find the correct column in the colSet_p.
Remove a column from the data file and the colSet_p. The DataManagerColumn object gets deleted..
Create a column in the storage manager on behalf of a table column. The caller has to delete the newly created object.
Create a scalar column.
Create a column in the storage manager on behalf of a table column. The caller has to delete the newly created object.
Create a direct array column.
Create a column in the storage manager on behalf of a table column. The caller has to delete the newly created object.
Create an indirect array column.
Get the cache object. This will construct the cache object if not present yet. The cache object will be deleted by the destructor.
Get the index object. This will construct the index object if not present yet. The index object will be deleted by the destructor.
Construct the cache object (if not constructed yet).
Construct the index object (if not constructed yet) and read it.
Read the index (at the end of the file).
Write the index (at the end of the file).