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

Generated by SchemaSpy on Mon Mar 08 13:39 PST 2010
Database Type: MySQL - 5.1.30-community
XML Representation Insertion Order Deletion Order (for database loading/purging scripts)

72 Tables:

Table	Children	Parents	Columns	Rows	Comments
aclobject	1		8	0
aclpermission		3	9	0	Security permissions
aclpermissionentry			11	1,219
attachment	4	2	13	5,007	File attachment information
baseline	2	1	11	102	Baselines
baseline_version		2	2	75,770	List of artifacts included in each baseline
changerequestassociation		4	10	0
distributiongroup	1	2	9	197	Email distribution groups for outbound email notification
distributiongroup_user		2	2	585	Users associated with distribution groups
document	15	21	80	397,512	Artifacts such as requirements, use cases etc
document_attachment		2	9	304	File attachments
document_docattach		2	8	1,889
document_document		5	12	139,492	Relationships between artifacts
document_tag		2	7	2,041	Tags
document_url		1	8	28
documentcustomfieldvalue		1	8	6,114
documentfield	2		18	129	Configuration table that
documentgroup	3	2	17	3,493	Primary groups table
documenttype	3		15	2,407	Indicates the type of artifact such as a requirement
documenttypefielddefinition		2	23	20,772	Configuration of the fields for each artifact
email		1	12	34,709
estimate		1	8	0	NO LONGER USED
eventactiontype			7	54
evententry		5	17	147,326	Event log - populates What's New
eventtype			9	10
filter		2	13	1,672	Filters
glossaryitem		1	8	97	NO LONGER USED
integrationcomponentmapping	1	2	13	0
integrationconnection		2	16	0
integrationdirectiontype	2		6	4
integrationfieldmapping		4	13	0
integrationtype	3		6	1
jamaauthprovider			15	0
jamacomment		2	9	6,502	Comments
jamaview	4	2	15	26
jobschedule	1		13	6
lookup	22	1	13	30,663
lookuptype	1		13	8,960
objecttype			9	16
organization	6		10	136	Organization - typically the company information
perspective	4	2	18	2
perspective_role		2	8	1
perspective_view		2	9	22
perspectiveconfig		2	11	10
perspectivetype	1		6	3
pluginentry			13	0
project	9	11	32	760	Project attributes
projectfield	1		11	27
projectrelease	3	1	12	1,173	Releases per project
projecttype	2		13	202
projecttypefield		2	22	1,811
propertyentry			10	1,072	Table that stored system properties used by Contour
relationshiptype	1		15	705
releasetype	1		11	627	Drop down list values specific to reases
report	2	3	17	40	Reports
report_criterion		1	2	47	Criteria for each report
report_reportformat		2	2	115
reportformat	1		9	5
reporttype	1		6	2
role	3		10	226	Roles or user groups defined by administrators
signature		2	11	0
subscription		1	8	255
tag	1		8	349	Tags
testresult		2	10	11,895	Test results
user_job		2	8	103
user_organization		2	8	0
user_role		2	2	1,359	User assignments to roles by project
userbase	18	2	24	1,365	Users
version	3	2	10	150,495	Master versioning table that associates an item with its versions
view_itemtype		1	11	2
viewconfig		2	11	37
viewtype	1		6	8

Columns: 859 Rows: 1,059,961