Contour Data Schema

This document outlines the data type conventions and tables in the Contour database schema.Some information like column indexes and foreign keys are omitted.Data types may differ slightly depending on which database is being used.

Tips

1.1 Boolean Values

Boolean Values are always represented by a T for true and F for false.

1.2 RefID & Scope Columns

You will notice that several columns include a RefId and Scope column. For certain tables the records can be configured to correspond to the project, organization or system.

The scope field may have the following values:

System
Organization Level
Project
Document Group (Not currently used)
Item (Not currently used)
User (Not currently used)

When writing queries, keep the scope in mind as this will indicate which table to join the ID to obtain the information.For example,if a lookup type has a scope of 2 that means the lookup is used across the entire organization. If the lookup type has a scope of 3 it's unique to each project.

1.3 Naming Conventions

Tables with an underscore such as are link tables that join data together.

Generated by
SchemaSpy


Things that might not be 'quite right' about your schema:

Columns whose name and type imply a relationship to another table's primary key:
Anomaly not detected
Tables without indexes:
Anomaly not detected
Columns that are flagged as both 'nullable' and 'must be unique':
Anomaly not detected
Tables that contain a single column:
Anomaly not detected
Tables with incrementing column names, potentially indicating denormalization:

Table

document

project

2 instances of anomaly detected
Columns whose default value is the word 'NULL' or 'null', but the SQL NULL value may have been intended:
Anomaly not detected