[GUSDEV] Preliminary 3.5 Schema

[Michael S. <msa...@pc...>]

All,

Development work on the GUS 3.5 Schema is nearing completion, and we'd 
like to take this opportunity to solicit community feedback and provide 
the 3.5 schema for review.

With the 3.5 Schema nearly finalized, we're now turning our attention to 
ensuring compatibility in the object layer and with plugins for 3.5. 
Once done, GUS 3.5 will be ready for release.  It's my hope that that 
will be as soon as possible, but I'm hesitant to give a firm date.

The attached file contains the 3.5 schema, in a simple text summary 
format.  When reviewing the file, please keep the following in mind:

* I've done a very preliminary analysis of the file--- there may be 
glaring mistakes/omissions.

* All tables and views in GUS 3.5 are versioned, and the version 
tables/views are not displayed.

* All tables and views in GUS 3.5 contain the standard housekeeping 
columns, which are also not displayed.

* Subclass tables (marked by "extends superclass" where superclass is 
the name of the parent table) only have the columns added by the 
subclass displayed.  For example, if the superclass has columns a, b, c, 
and d, then the subclass will display the column e but have all five 
columns in the database.

* This is an object-centric display-- the method of subclassing (i.e. 
use of imp tables) is not changing.  As a result, Imp tables are not 
displayed, nor are super/sub classes flagged as views.

* The Type of a column with a foreign key is the name of the foreign key 
table.  For example, a table with a column NA_FEATURE_ID with a foreign 
key to DoTS.NAFEATURE will have a type of DoTSS.NAFEATURE.  This is the 
only way foreign keys are displayed in this view.

* All tables first column serves as the Primary key.  There is no 
denotation for the primary key (although it will also appear as an index 
against the first column).  Some tables are missing primary keys in this 
document-- it will be fixed soon.

* All indexes for a table are displayed.

Please let me know if you have any questions/concerns.

Thanks,

Mike