Table cxgn.public.featureprop

A feature can have any number of slot-value property tags attached to it. This is an alternative to hardcoding a list of columns in the relational schema, and is completely extensible

Generated by
SchemaSpy
Related columns Constraint names Comments Legend
Legend: SourceForge.net
Primary key columns
Columns with indexes
Implied relationships
Excluded column relationships
Dashed lines show
implied relationships
< n > number of related tables
Please support this project 
Column Type Size Nulls Auto Default Children Parents Comments
featureprop_id serial 10  √  nextval('featureprop_featureprop_id_seq'::regclass)
featureprop_pub.featureprop_id featureprop_pub_featureprop_id_fkey
feature_id int4 10
feature.feature_id featureprop_feature_id_fkey
type_id int4 10
cvterm.cvterm_id featureprop_type_id_fkey
The name of the
property/slot is a cvterm. The meaning of the property is defined in
that cvterm. Certain property types will only apply to certain feature
types (e.g. the anticodon property will only apply to tRNA features) ;
the types here come from the sequence feature property ontology
value text 2147483647  √  null The value of the property, represented as text. Numeric values are converted to their text representation. This is less efficient than using native database types, but is easier to query.
rank int4 10 0 Property-Value ordering. Any
feature can have multiple values for any particular property type -
these are ordered in a list using rank, counting from zero. For
properties that are single-valued rather than multi-valued, the
default 0 value should be used

Table contained 2,474 rows at Fri Sep 05 01:31 EDT 2008

Indexes:
Column(s) Type Sort Constraint Name
featureprop_id Primary key Asc featureprop_pkey
feature_id + type_id + rank Must be unique Asc/Asc/Asc featureprop_c1
feature_id Performance Asc featureprop_idx1
type_id Performance Asc featureprop_idx2

Close relationships  within one two degrees of separation :