Schema for mrnaOrientInfo
  Database: cb1    Primary Table: mrnaOrientInfo    Row Count: 542   Data last updated: 2017-01-02
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 75smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 2292071int(10) unsigned range Start position in chromosome
chromEnd 2564726int(10) unsigned range End position in chromosome
name U48289varchar(255) values Accession of EST
intronOrientation 2smallint(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 19smallint(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
        cb1.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
75chrUn22920712564726U48289200190
602chrUn23004782304279AF3155554140360
75chrUn23787302913420AF4994388150330
613chrUn37372413739503AY363116105000
615chrUn39582243958914EF09025920000
628chrUn57340505735594AJ24563340000
632chrUn61942706197674AJ88799490000
635chrUn66147716616525AY363117630250
642chrUn75973247597897AF50702210000
652chrUn87992168800413DQ48205910000

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