Table cxgn.public.feature_cvterm

Associate a term from a cv with a feature, for example, GO annotation

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
feature_cvterm_id serial 10  √  nextval('feature_cvterm_feature_cvterm_id_seq'::regclass)
feature_cvterm_dbxref.feature_cvterm_id feature_cvterm_dbxref_feature_cvterm_id_fkey
feature_cvterm_pub.feature_cvterm_id feature_cvterm_pub_feature_cvterm_id_fkey
feature_cvtermprop.feature_cvterm_id feature_cvtermprop_feature_cvterm_id_fkey
feature_id int4 10
feature.feature_id feature_cvterm_feature_id_fkey
cvterm_id int4 10
cvterm.cvterm_id feature_cvterm_cvterm_id_fkey
pub_id int4 10
pub.pub_id feature_cvterm_pub_id_fkey
Provenance for the annotation. Each annotation should have a single primary publication (which may be of the appropriate type for computational analyses) where more details can be found. Additional provenance dbxrefs can be attached using feature_cvterm_dbxref
is_not bool 1 false if this is set to true, then this annotation is interpreted as a NEGATIVE annotation - ie the feature does NOT have the specified function, process, component, part, etc. See GO docs for more details

Table contained 0 rows at Wed May 20 01:40 EDT 2009

Indexes:
Column(s) Type Sort Constraint Name
feature_cvterm_id Primary key Asc feature_cvterm_pkey
feature_id + cvterm_id + pub_id Must be unique Asc/Asc/Asc feature_cvterm_c1
feature_id Performance Asc feature_cvterm_idx1
cvterm_id Performance Asc feature_cvterm_idx2
pub_id Performance Asc feature_cvterm_idx3

Close relationships  within one two degrees of separation :