Schema for mrnaOrientInfo
  Database: tetNig2    Primary Table: mrnaOrientInfo    Row Count: 106,230   Data last updated: 2019-09-21
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 106851int(10) unsigned range Start position in chromosome
chromEnd 107537int(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 3smallint(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)
      tetNig2.all_mrna.qName (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
585chr1106851107537CR683322030240
586chr1164887168381CR691867820260
586chr1164887168457CR729394820260
586chr1214055214981CR69646902000
586chr1214055214988CR70339002000
587chr1283552285874CR63608350000
587chr1283572287302CR661017110000
587chr1285072287261CR68364080000
587chr1316096316864CR70682300000
587chr1316096316864CR71005000000

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