|STAR Computing||Tutorials main page|
|DataBase Data Definitions|
|Offline computing tutorial||Maintained by Jeff Porter|
|Last modified Fri Jul 03 00:19:00 1998|
Data Type Definitions
As of April-May'99, Star database efforts moved away from an Object-Oriented
Database infrastructure (Objectivity) to a Relational-DB structure (MySQL).
This switch was done because a Relational-DB model is a much simpler match
to the requirements of handling traditional database data - as distinguished
from the data-handling that Objectivity was envisioned to provide in the full
Star Event Data Store. The dropping of Objectivity as the tool for the Star
Event Store (a post-MDC2 decision) triggered the decision to also drop it as
the storage tool for traditional database uses. |
Prior to this decision, but in recognition that such a decision was likely, the database and calibrations group had decided that the low-level storage structure would be based on Tables (e.g. c-structs) that are defined in header (*.h) files.
Example: tpcDriftVelocity definition in tpcDriftVelocity.h
Database Data Objects
Database Data Objects specify the time referenced status of the detector & subsystems. Each object contains a unique set of data-elements that are identified by the object-name. The data-values for an object vary with time & versioning and thus the data access API requires this complete identification
Database Data Objects' object-name includes the c-struct name associated with the group of data elements contained within the object. Multiple cases of the same class that are used for different objects must provide name-checking accessor to distinguish the different named objects.
Database Data Objects' definition is supplied in a header file that specifies the data-elements and auxiliarly information such as descriptive comments about the data.
Meta data used to organized, manage, and navigate the database data objects are generally also Database Data Objects and where appropriate adhere to the conventions noted here.