Schema for mrnaOrientInfo
  Database: chlSab2    Primary Table: mrnaOrientInfo    Row Count: 728   Data last updated: 2019-06-29
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 587smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chr1varchar(255) values Reference sequence chromosome or scaffold
chromStart 344646int(10) unsigned range Start position in chromosome
chromEnd 344726int(10) unsigned range End position in chromosome
name AJ437019varchar(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 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
        chlSab2.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
587chr1344646344726AJ43701900000
589chr1639410645137AF275666710000
601chr121911142211307AF11659970000
636chr167746526783063AF090949519000
648chr183697748374239AF010188900160
651chr186866368700472AF395658200000
660chr199129979917266AF11073650000
680chr11250886412543123L202162500210
703chr11558284215584169AB16098030000
1050chr16105054961067265AB21005050000

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