Schema for mrnaOrientInfo
  Database: caeRem3    Primary Table: mrnaOrientInfo    Row Count: 604   Data last updated: 2016-05-28
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 585smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 9279int(10) unsigned range Start position in chromosome
chromEnd 10247int(10) unsigned range End position in chromosome
name EU183220varchar(255) values Accession of EST
intronOrientation 3smallint(6) range Orientation of introns with respect to EST
sizePolyA 0smallint(6) range Number of trailing A's
revSizePolyA 0smallint(6) range Number of trailing A's on reverse strand
signalPos 0smallint(6) range Position of start of polyA signal relative to end of EST or 0 if no signal
revSignalPos 0smallint(6) range PolyA signal position on reverse strand if any

Connected Tables and Joining Fields
        caeRem3.all_mrna.qName (via mrnaOrientInfo.name)
      hgFixed.gbCdnaInfo.acc (via mrnaOrientInfo.name)
      hgFixed.gbSeq.acc (via mrnaOrientInfo.name)
      hgFixed.imageClone.acc (via mrnaOrientInfo.name)
      hgFixed.refLink.mrnaAcc (via mrnaOrientInfo.name)
      hgFixed.refSeqStatus.mrnaAcc (via mrnaOrientInfo.name)
      hgFixed.refSeqSummary.mrnaAcc (via mrnaOrientInfo.name)
      knownGeneV39.kgXref.refseq (via mrnaOrientInfo.name)
      knownGeneV39.knownToRefSeq.value (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
585chrUn927910247EU18322030000
585chrUn2576327778DQ86889560000
585chrUn3028332288DQ86889660000
586chrUn135973137340EU16551630000
586chrUn224168224896DQ06025610100
587chrUn293666295415DQ11535560000
588chrUn510313512922FJ80483790000
588chrUn510313512922FJ80483890000
588chrUn510313512922FJ80483990000
588chrUn510313512922FJ80484090000

Note: all start coordinates in our database are 0-based, not 1-based. See explanation here.