Schema for mrnaOrientInfo
  Database: gadMor1    Primary Table: mrnaOrientInfo    Row Count: 77,822   Data last updated: 2020-08-19
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 CAEA01000002varchar(255) values Reference sequence chromosome or scaffold
chromStart 23int(10) unsigned range Start position in chromosome
chromEnd 763int(10) unsigned range End position in chromosome
name JW177192varchar(255) values Accession of EST
intronOrientation 1smallint(6) range Orientation of introns with respect to EST
sizePolyA 1smallint(6) range Number of trailing A's
revSizePolyA 2smallint(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
        gadMor1.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
585CAEA0100000223763JW17719211200
585CAEA010000160172JW21221700000
585CAEA010000190467JW18889911000
585CAEA0100007122682434JW192848000140
585CAEA0100008447339JW19292700000
585CAEA01000098896997JW176862070220
585CAEA010001023287JW18215500000
585CAEA010001528771177JW20024500000
585CAEA010001670378JW17918210000
585CAEA01000172209398JW17972200100

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