Schema Version: 1.3



In addition to the primary identifier (cvterm.dbxref_id) a cvterm can have zero or more secondary identifiers/dbxrefs, which may refer to records in external databases. The exact semantics of cvterm_dbxref are not fixed. For example: the dbxref could be a pubmed ID that is pertinent to the cvterm, or it could be an equivalent or similar term in another ontology. For example, GO cvterms are typically linked to InterPro IDs, even though the nature of the relationship between them is largely one of statistical association. The dbxref may be have data records attached in the same database instance, or it could be a "hanging" dbxref pointing to some external database. NOTE: If the desired objective is to link two cvterms together, and the nature of the relation is known and holds for all instances of the subject cvterm then consider instead using cvterm_relationship together with a well-defined relation.


Column Type Size Foreign Key Nullable Default Comments
cvterm_dbxref_id bigserial 19
cvterm_id int8 19
cvterm.cvterm_id cvterm_dbxref_cvterm_id_fkey C
dbxref_id int8 19
dbxref.dbxref_id cvterm_dbxref_dbxref_id_fkey C
is_for_definition int4 10

A cvterm.definition should be supported by one or more references. If this column is true, the dbxref is not for a term in an external database - it is a dbxref for provenance information for the definition.

Table contained -1 rows


Constraint Name Type Sort Column(s)
cvterm_dbxref_pkey Primary key Asc cvterm_dbxref_id
cvterm_dbxref_c1 Must be unique Asc/Asc cvterm_id + dbxref_id
cvterm_dbxref_idx1 Performance Asc cvterm_id
cvterm_dbxref_idx2 Performance Asc dbxref_id