Columns
| Column | Type | Size | Foreign Key | Nullable | Default | Comments | ||
|---|---|---|---|---|---|---|---|---|
| feature_synonym_id | bigserial | 19 |
|
nextval('chado.feature_synonym_feature_synonym_id_seq'::regclass) | ||||
| synonym_id | int8 | 19 |
|
null | ||||
| feature_id | int8 | 19 |
|
null | ||||
| pub_id | int8 | 19 |
|
null | The pub_id link is for relating the usage of a given synonym to the publication in which it was used. |
|||
| is_current | bool | 1 |
|
false | The is_current boolean indicates whether the linked synonym is the current -official- symbol for the linked feature. |
|||
| is_internal | bool | 1 |
|
false | Typically a synonym exists so that somebody querying the db with an obsolete name can find the object theyre looking for (under its current name. If the synonym has been used publicly and deliberately (e.g. in a paper), it may also be listed in reports as a synonym. If the synonym was not used deliberately (e.g. there was a typo which went public), then the is_internal boolean may be set to -true- so that it is known that the synonym is -internal- and should be queryable but should not be listed in reports as a valid synonym. |
Table contained -1 rows
Indexes
| Constraint Name | Type | Sort | Column(s) |
|---|---|---|---|
| feature_synonym_pkey | Primary key | Asc | feature_synonym_id |
| feature_synonym_c1 | Must be unique | Asc/Asc/Asc | synonym_id + feature_id + pub_id |
| feature_synonym_idx1 | Performance | Asc | synonym_id |
| feature_synonym_idx2 | Performance | Asc | feature_id |
| feature_synonym_idx3 | Performance | Asc | pub_id |
Relationships
The following entity relationship (ER) diagram shows the relationships involving the feature_synonym table.
Show relationships within degrees of separation
