Schema database

Schema database along with the Component is the core of the DB3NF infrastructure. It serves two purposes. Firstly, schema database stores the entire application schema that is accessible by the Component, and that is how the Web application "learns" what it is supposed to do and what the rules are. Secondly, schema database builds, through its stored procedures library, the whole "Data" database, including stored procedures.

CLASS_TYPES table stores all the classes of the application. In this site example these are user, group, firm

CLASS_RULES table establishes relationship between classes. In our sample user belongs to a single firm and any number of groups.

PROPERTY_TYPES lists all the properties used in the application, such as username, First name, Age, ZIP, e-mail, etc. For each property there is a data type, range of values, description, presentation attributes, and for some properties, a list of value options.

PROPERTY_RULES table "connects" properties to classes, i.e. Age is a property of User. It also specifies whether a property is required and puts properties in desired order.

PROPERTY_OPTIONS and PROPERTY_OPTION_VALUES list options for some properties like in our sample Country. When Country is displayed in a form, the data originates in these tables.

DATA_TYPES and DISPLAY_TYPES tables list possible values for related columns in PROPERTY_TYPES table.

DEPLOYMENT_OPTIONS table stores data used in deployment process.