| Data Model Subset System |
[This is preliminary documentation and is subject to change.]
This subset of the static data model is just used to group miscellaneous database tables, that do not fit in the other groups (subsets).
Since these tables do nat have any relation to each other, data model diagrams (in E-R or UML Class notation) are not relevant here.
Table | Usage |
|---|---|
Holds the data model version number (a text string in the format "<majorversion>.<minorversion>"). This value is automatically inserted / updated by the database creation / update procedure. A given data model version number identifies a physical database structure (tables, views, functions, stored procedures, etc.) Do NOT edit these values manually (unless you really know what you are doing). It is of vital importance for the function of the TOPICA framework, that the data model version number corresponds to the actual database objects! | |
Look-up table for sex. The names (not the numbers!) may be edited for localization purposes. | |
The online deployment functionality makes it possible to deploy configuration items from one configuration (source) to another (target) - across networks. For each deployment target, information on URL, username, password etc. must be supplied. This tables is used to store this information, so that the user (deployer) does not have to key in this information on each deployment. | |
State machines are configuration items, that are defined in XML files. State machines contain states (obviously). For reports etc., where data is fetched from the database using SQL, it is often necessary to get state names. This table holds the state names making this possible. | |
Holds ZIP codes (code and text), when the codes are numeric. Alphanumeric ZIP codes (as in the UK) are currently not supported. |