| feature_relationship_id |
serial |
10 |
|
√ |
nextval('feature_relationship_feature_relationship_id_seq'::regclass) |
|
|
|
| subject_id |
int4 |
10 |
|
|
null |
|
| feature.feature_id |
feature_relationship_subject_id_fkey |
C |
|
the subject of the subj-predicate-obj sentence. This is typically the subfeature |
| object_id |
int4 |
10 |
|
|
null |
|
| feature.feature_id |
feature_relationship_object_id_fkey |
C |
|
the object of the subj-predicate-obj sentence. This is typically the container feature |
| type_id |
int4 |
10 |
|
|
null |
|
| cvterm.cvterm_id |
feature_relationship_type_id_fkey |
C |
|
relationship type between subject and object. This is a cvterm, typically from the OBO relationship ontology, although other relationship types are allowed. The most common relationship type is OBO_REL:part_of. Valid relationship types are constrained by the Sequence Ontology |
| value |
text |
2147483647 |
√ |
|
null |
|
|
Additional notes/comments |
| rank |
int4 |
10 |
|
|
0 |
|
|
The ordering of subject features with respect to the object feature may be important (for example, exon ordering on a transcript - not always derivable if you take trans spliced genes into consideration). rank is used to order these; starts from zero |
