Schema for mrnaOrientInfo
  Database: cb3    Primary Table: mrnaOrientInfo    Row Count: 545   Data last updated: 2016-12-31
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 chrIvarchar(255) values Reference sequence chromosome or scaffold
chromStart 66575int(10) unsigned range Start position in chromosome
chromEnd 68475int(10) unsigned range End position in chromosome
name DQ482074varchar(255) values Accession of EST
intronOrientation 1smallint(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
        cb3.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
585chrI6657568475DQ48207410000
585chrI6657568475DQ48207520000
585chrI107907109248DQ48209011000
585chrI107907109248DQ48209121000
609chrI31717123174561AY5895979220438
609chrI31941613197640AF03003780000
620chrI46932244696335AY589606516008
626chrI53905575391955DQ48207621000
626chrI53905575391955DQ48207731000
626chrI53905575391955DQ48207831000

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