This is the test server for the new GMOD.org server. Please be aware that changes to pages here might get lost.
- The module page for the module the table is a part of. This is where updates and comments should be posted.
- The Chado Tables page, which lists all tables.
You can include this template anywhere you want to show the table description.
A feature is a biological sequence or a section of a biological sequence, or a collection of such sections. Examples include genes, exons, transcripts, regulatory regions, polypeptides, protein domains, chromosome sequences, sequence variations, cross-genome match regions such as hits and HSPs and so on; see the Sequence Ontology for more. The combination of organism_id, uniquename and type_id should be unique.
|feature_id||serial|| PRIMARY KEY|
|dbxref||dbxref_id||integer|| An optional primary public stable
identifier for this feature. Secondary identifiers and external dbxrefs go in the table feature_dbxref.
|name||character varying(255)|| The optional human-readable common name for
a feature, for display purposes.
|residues||text|| A sequence of alphabetic characters
representing biological residues (nucleic acids, amino acids). This column does not need to be manifested for all features; it is optional for features such as exons where the residues can be derived from the featureloc. It is recommended that the value for this column be manifested for features which may may non-contiguous sublocations (e.g. transcripts), since derivation at query time is non-trivial. For expressed sequence, the DNA sequence should be used rather than the RNA sequence. The default storage method for the residues column is EXTERNAL, which will store it uncompressed to make substring operations faster.
|seqlen||integer|| The length of the residue feature. See
column:residues. This column is partially redundant with the residues column, and also with featureloc. This column is required because the location may be unknown and the residue sequence may not be manifested, yet it may be desirable to store and query the length of the feature. The seqlen should always be manifested where the length of the sequence is known.
|md5checksum||character(32)|| The 32-character checksum of the sequence,
calculated using the MD5 algorithm. This is practically guaranteed to be unique for any feature. This column thus acts as a unique identifier on the mathematical sequence.
|is_analysis||boolean|| NOT NULL|
|is_obsolete||boolean|| NOT NULL|
|timeaccessioned||timestamp without time zone|| NOT NULL|
|timelastmodified||timestamp without time zone|| NOT NULL|
Tables referencing feature via foreign key constraints: