Schema for mrnaOrientInfo
  Database: tetNig1    Primary Table: mrnaOrientInfo    Row Count: 108,241   Data last updated: 2019-09-22
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 chr1varchar(255) values Reference sequence chromosome or scaffold
chromStart 87816int(10) unsigned range Start position in chromosome
chromEnd 88505int(10) unsigned range End position in chromosome
name CR683322varchar(255) values Accession of EST
intronOrientation 0smallint(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 24smallint(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
        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)
      tetNig1.all_mrna.qName (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
585chr18781688505CR683322000240
586chr1145292148788CR691867800260
586chr1145292148864CR729394800260
586chr1186514187442CR69646900000
586chr1186514187449CR70339000000
586chr1256013258335CR63608350000
586chr1256033259763CR661017110000
586chr1257533259722CR68364080000
587chr1288557289325CR70682300000
587chr1288557289325CR71005000000

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