Schema for mrnaOrientInfo
  Database: caePb2    Primary Table: mrnaOrientInfo    Row Count: 198   Data last updated: 2011-03-29
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 588smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 393448int(10) unsigned range Start position in chromosome
chromEnd 394829int(10) unsigned range End position in chromosome
name EU726795varchar(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
        caePb2.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
588chrUn393448394829EU72679530000
593chrUn11250691125652EU72678500000
596chrUn14458481446835EU69292020000
596chrUn14668561467762EU71125520000
596chrUn14670791467819EU71126220000
610chrUn33488843349512EU6527461300500
610chrUn33489133349481EU71124810000
610chrUn33491823349512EU652739010401240
634chrUn64556596456501EU69292220000
635chrUn65718316572608EU69292420000

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