Schema for mrnaOrientInfo
  Database: anoGam3    Primary Table: mrnaOrientInfo    Row Count: 66,300   Data last updated: 2018-04-06
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 586smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chr2Lvarchar(255) values Reference sequence chromosome or scaffold
chromStart 203780int(10) unsigned range Start position in chromosome
chromEnd 204649int(10) unsigned range End position in chromosome
name BX047830varchar(255) values Accession of EST
intronOrientation 1smallint(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
        anoGam3.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
586chr2L203780204649BX04783010000
586chr2L203780204695BX047831-11100
586chr2L203798204646BX05296810100
586chr2L203806204695BX052969-10000
586chr2L204234205270BX036016000130
586chr2L204239205211BX02363100000
586chr2L204284205285BX036017001400
586chr2L204391205286BX02363200800
586chr2L207893209480BX04383040000
586chr2L208779209955BX043831-33000

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