 
 
 
-
-################################################################################
-#
-# Table structure for table 'repeat_consensus'
-#
-# repeat_class examples: SINE, LINE, DNA Transposon, Retroviral LTR,
-# Satellite, Tandem
+/**@table repeat_consensus
+@desc Stores consensus sequences obtained from analysing repeat features.
+
+@column repeat_consensus_id              Primary key, internal identifier.
+@column repeat_name                      Repeat name.
+@column repeat_class                     E.g. 'Satellite', 'tRNA', 'LTR'.
+@column repeat_type                      E.g. 'Satellite repeats', 'Tandem repeats', 'Low complexity regions'.
+@column repeat_consensus                 Repeat consensus sequence.
+
+*/
+
 
 CREATE TABLE repeat_consensus (
 




################################################################################
#
# Table structure for table 'splicing_transcript_pair'
#

CREATE TABLE splicing_transcript_pair (


) COLLATE=latin1_swedish_ci ENGINE=MyISAM;


/**@table coord_system
@desc Stores information about the available co-ordinate systems for the species identified through the species_id field.
Note that for each species, there must be one co-ordinate system that has the attribute "top_level" and one that has the attribute "sequence_level".

@column coord_system_id      Primary key, internal identifier.
@column species_id           Indentifies the species for multi-species databases.       
@column name                 Co-oridinate system name, e.g. 'chromosome', 'contig', 'scaffold' etc.     
@column version              Assembly.    
@column rank                 Co-oridinate system rank.   
@column attrib               Co-oridinate system attrib (e.g. "top_level", "sequence_level").     

@see seq_region - Has coord_system_id foreign key to allow joins with the coord_system table. 
@see meta - Holds meta information about each of the species in a database, no matter if it's a multi-species or single-species database.

*/


CREATE TABLE coord_system (

