Schema for mrnaOrientInfo
  Database: caePb1    Primary Table: mrnaOrientInfo    Row Count: 198   Data last updated: 2016-05-27
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 587smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 317011int(10) unsigned range Start position in chromosome
chromEnd 317639int(10) unsigned range End position in chromosome
name EU652746varchar(255) values Accession of EST
intronOrientation 1smallint(6) range Orientation of introns with respect to EST
sizePolyA 30smallint(6) range Number of trailing A's
revSizePolyA 0smallint(6) range Number of trailing A's on reverse strand
signalPos 50smallint(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
        caePb1.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
587chrUn317011317639EU6527461300500
587chrUn317040317608EU71124810000
587chrUn317309317639EU652739010401240
594chrUn12534441254825EU72679530000
600chrUn20048512005434EU72678500000
612chrUn36319063632802EU72678622000
620chrUn46132854614062EU69292420000
623chrUn50098225011546EU65274030000
625chrUn52542705254644EU63789610000
629chrUn58086445809484EU69291030000

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