Schema for mrnaOrientInfo
  Database: priPac1    Primary Table: mrnaOrientInfo    Row Count: 136   Data last updated: 2016-12-29
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 chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 25446int(10) unsigned range Start position in chromosome
chromEnd 27769int(10) unsigned range End position in chromosome
name EF634531varchar(255) values Accession of EST
intronOrientation 2smallint(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
        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)
      priPac1.all_mrna.qName (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
585chrUn2544627769EF63453120000
585chrUn8671691738AY835965170000
611chrUn34880043507177JQ9462901800180
621chrUn47751204775461EF63479710000
654chrUn90905519091422EF63460720000
657chrUn94730079487996AY862499130000
696chrUn1455067314551370EF63489220000
701chrUn1527155315278822AY21667960008
711chrUn1663826616644621FJ8951001024000
711chrUn1663826616644621FJ8951041024000

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