Schema for mrnaOrientInfo
  Database: fr2    Primary Table: mrnaOrientInfo    Row Count: 1,406   Data last updated: 2020-05-07
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 589smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 617689int(10) unsigned range Start position in chromosome
chromEnd 622143int(10) unsigned range End position in chromosome
name AB179548varchar(255) values Accession of EST
intronOrientation 8smallint(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
        fr2.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
589chrUn617689622143AB17954880000
591chrUn876958878823AB256950800170
592chrUn961599963063DQ41300020000
593chrUn10967981098619EF37136610000
603chrUn24481962449132LC1292292250410
604chrUn25271172531899AY29875180000
610chrUn32878033305408AB236415190000
612chrUn35406843544302AY5294853170400
615chrUn39611313963631AB330136731000
616chrUn41171274120573HF93668360000

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