DatabaseInterface Namespace Reference

Concept Package-wide namespace of utilities and typedef/enums. More...


Detailed Description

Concept Package-wide namespace of utilities and typedef/enums.

Concept Templated class of pointers to Writer objects. Writer objects are lightweight and provide type safe write access to a single validity set of a specific table. A DbiWriter knows about publishing protocols but uses a DbiSqlValPacket both to hold the data in a type- neutral form and to do the actual I/O.

Concept A set of DbiValidityRecs

Concept Constructor for the set of effective DbiValidityRec objects for the current query.

Concept A concrete data type corresponding to a single row in an auxillary validity range database table.

Concept Abstract interface to TableRow objects. Each database table consists of a collection of TableRow objects.

Concept Factory creating DbiTableProxy objects.

Concept Table meta data i.e. data about the table itself

Concept Output string stream - string that can be assembled from basic types.

Concept A connected reusable statement with accompanying exception log. After deleting, the associated server connection is dropped if then idle. Limited support for SQL translation between MySQL and other dialects.

Concept The SQL statements to generate a Validity Packet i.e a single DbiValidityRec row and its associated main table data rows.

Concept Association of a particular SimFlag type with a list of SimFlag types.

Concept Register of support services.

Concept I/O buffer for a row of a table.

Concept A register of rollback dates organised by table name

Concept Input stream with type checking.

Concept Templated class of pointers to Result objects. ResultPtr objects are lightweight and provide type safe access to a specific table.

Concept ResultNonAgg is a concrete sub-class of DbiResult that represents a single database query for a non-aggregated table.

Concept Summarises the composition of a single DbiResult.

Concept // Concept: ResultAgg is a concrete sub-class of DbiResult that represents a single database query for either:-

Concept Abstract base class representing the Result of a single database query. If query suceeded the Result will hold (own) a vector of table row objects that correspond to result of the query. It will also own a DbiValidityRec that gives the range over which the result is valid.

Concept Record of all the query results currently in memory.

Concept Output stream for the values of a single table row with type checking and deferred sequence number asignment.

Concept An single entry in the Database Log which records all non-automatic updates to the database.

Concept Database neutral table column field types.

Concept An object that records database exceptions

Concept An object that records a single database exception.

Concept Object to query a specific database table.

Concept An object that hold open all DbiConnections throught its lifetime.

Concept A managed TSQLServer connection- dropped when idle.

Concept I/O of configuration data and equivalent Registry objs.

Concept A concrete data type corresponding to a single row in a database table of configuration data.

Concept A cascade (prioritorised list) of DbiConnections, one for each database in the cascade.

Concept Cache holding DbiResults for a specific database table.

Concept Binary file for reading/writing Dbi related objects.

Concept A helper class to prepare an ASCII database table file for importing

Concept A utility to prepare an ASCII database from a a collection of ASCII files.

Purpose To provide standard of utilities and typedef/enums. Contact: n.west1@physics.ox.ac.uk

Purpose To prepare a temporary (process specific) ASCII database. Acknowledgments The code is essentially a translation of RDBC/TSQLImporter by Valeriy Onuchin 21/03/2001 Contact: n.west1@physics.ox.ac.uk

Purpose To simplifly the construction of a temporary (process specific) ASCII database. Acknowledgments The code is essentially a translation of RDBC/TSQLImporterClient by Valeriy Onuchin 21/03/2001 Contact: n.west1@physics.ox.ac.uk

Purpose To save/restore cache to speed up startup when running in the same context. Contact: n.west1@physics.ox.ac.uk

Purpose A DbiCache is an object that minimises database I/O by caching query results. Queries are always first sent to the cache and only if not present are they sent down to the database. Contact: n.west1@physics.ox.ac.uk

Purpose Implements the concept of a cascade allowing user to overrride parts of the standard database by introducing higher priority non-standard ones above it in a cascade. Contact: n.west1@physics.ox.ac.uk

Purpose Table row proxy for all AlgConfig data. Contact: n.west1@physics.ox.ac.uk

Purpose Used to fill/store Registry objects. Contact: n.west1@physics.ox.ac.uk

Purpose To minimise connections, particularly to ORACLE servers where connections cost money! Contact: n.west1@physics.ox.ac.uk

Purpose To minimse the number of connections made and broken when performing multiple SQL queries. Contact: n.west1@physics.ox.ac.uk

Purpose To encapsulate the standard context query and the management of SEQNOs and meta-data. This allows clients to execute queries without specifying SQL. DbiDBProxy also supports "Extended Context" queries which provides a framework in which clients can extended the basic query and can use SQL to fine tune their requests. Uage Notes The object can be "programmed" with an SQL condition using SetSqlCondition. If not null the string is prefixed with "where" and used when responding to the following validity queries:- QueryAllValidities QueryValidity Contact: n.west1@physics.ox.ac.uk

PurposeTo provide a place to record an exception. Currently ROOT's SQL package does not have a class for this information, instead it is embedded in TSQLServer and TSQStatement. Contact: n.west1@physics.ox.ac.uk

PurposeTo provide a place to record exceptions from the time they arise in the lower levels of the DBI and below until they can be analysed in the upper levels of the DBI and beyond Contact: n.west1@physics.ox.ac.uk

Purpose To provide mappings and check compatibility between database types and application types. Contact: n.west1@physics.ox.ac.uk

Purpose Capture and present updates together with the reasons for them. Contact: n.west1@physics.ox.ac.uk

Purpose This is a helper class for DbiSqlValPacket. Its primary purpose is to provide an << operator with built-type checking to simplify the writing of DbiTableRow subclasses. Contact: n.west1@physics.ox.ac.uk

Purpose To determine, from a production file, what database data were used during processing. Contact: n.west1@physics.ox.ac.uk

Purpose To provide suitable objects to cache. DbiResults can be checked to see if they satisfy new queries. Contact: n.west1@physics.ox.ac.uk

1) A specific context with aggregated data (i.e. rows with AggNo != -1)

or:-

2) Any extended context query, even if that only produces a single row of unaggregated data.

The table is indexed using the index returned by DbiTableRow::GetIndex which can be overridden by concrete subclasses.

Purpose To present the user with a single logical table even though the component parts may held in multiple DbiResults and be be loaded by separate I/O operations. Contact: n.west1@physics.ox.ac.uk

Purpose To serve as the data members of a DbiRecord (q.v.). Contact: n.west1@physics.ox.ac.uk

Purpose See DbiResult. Contact: n.west1@physics.ox.ac.uk

Purpose ResultPtrs are the primary application interface to the Dbi. Users instantiate ResultPtrs with the information necessary define a table query and then interrogate the object for the results. Contact: n.west1@physics.ox.ac.uk

Purpose This is an interface to TSQLResultSet. Its primary purpose is to provide an >> operator with built-type checking to simplify the writing of DbiTableRow subclasses. Contact: n.west1@physics.ox.ac.uk

Purpose Simplify rollback date management by extracting info. from DBI registry and serving by table name Contact: n.west1@physics.ox.ac.uk

Purpose This forms the base class for DbiResultSet (input) and DbiWriter (input) Contact: n.west1@physics.ox.ac.uk

Purpose To break dependency loops and to simplify communication of some elements of the global environment, DbiTableProxyRegistry registers some support services and environment with DbiServices, a class which only contains static methods. Other Dbi classes can then obtain the necessary information from DbiServices and avoids having those classes ask DbiTableProxyRegistry directly. Contact: n.west1@physics.ox.ac.uk

Purpose To allow the DBI to choose an alternative SimFlag type when attempting to satisfy queries. For example, allow MC data to use Data constants. Contact: n.west1@physics.ox.ac.uk

Purpose Used as part of database maintenance as the unit of transfer between databases. Contact: n.west1@physics.ox.ac.uk

Purpose To minimise connections, particularly to ORACLE servers where connections cost money, and to simplify interfacing to different database backends. Contact: n.west1@physics.ox.ac.uk

Purpose This is used to assemble SQL commands. It was written to plug what was then a deficiency in gcc ostrstream. It could be removed now if I had the energy. Contact: n.west1@physics.ox.ac.uk

Purpose To provide information on the names and types of columns Contact: n.west1@physics.ox.ac.uk to transient DbiRowStream objects.

Purpose A DbiTableProxy is an object that knows how to send queries to a specific database table. Internally it uses a cache to minimise I/O. Contact: n.west1@physics.ox.ac.uk

Purpose A DbiTableProxyRegistry is a factory that creates and owns, DbiTableProxys for all database tables. Contact: n.west1@physics.ox.ac.uk

Purpose Provides a generic interface to TableRow objects permiting much of the database machinery to be generic. Subclass obligations All subclasses must have public default and constructors. Program Notes It inherits from TObject only so that it can get the class name at execution time. Contact: n.west1@physics.ox.ac.uk

Purpose To resolve ambiguities in the case of multiple matches to a query and to record results of validity range trimming due to neighbouring database entries. Contact: n.west1@physics.ox.ac.uk

Purpose Parse a DbiResultSet from a validity query and build DbiValidityRecs for the best, with VldRange trimmed by neighbouring validity records of higher priority. For non-aggregated tables there will only be one DbiValidityRec, but for aggregated data, there will be one for each aggregate Contact: n.west1@physics.ox.ac.uk

Purpose Provides a sequential access mechanism for an entire table via its auxillary Validity Range table Contact: n.west1@physics.ox.ac.uk

Purpose Writers are the primary application output interface to the Dbi. Users instantiate Writers with the information necessary define a validity set and then pass all the rows one at a time, to the writer. The user is able to abort the process at any point before the final commit. Contact: n.west1@physics.ox.ac.uk


Generated on 24 Jul 2018 for loon by  doxygen 1.6.1