Schema for mrnaOrientInfo
  Database: melUnd1    Primary Table: mrnaOrientInfo    Row Count: 30   Data last updated: 2018-10-23
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 JH537067varchar(255) values Reference sequence chromosome or scaffold
chromStart 827int(10) unsigned range Start position in chromosome
chromEnd 1001int(10) unsigned range End position in chromosome
name Y11787varchar(255) values Accession of EST
intronOrientation 0smallint(6) range Orientation of introns with respect to EST
sizePolyA 19smallint(6) range Number of trailing A's
revSizePolyA 1smallint(6) range Number of trailing A's on reverse strand
signalPos 41smallint(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)
      melUnd1.all_mrna.qName (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
585JH5370678271001Y117870191410
585JH538811163569KM52287311000
585JH5497649691179AY2420590250480
585JH553121333463KM52287300000
586JH556348192861198187Y117871180410
591JH556417836598840663AB46869550000
590JH556451701988705274AF02124140000
73JH556554777486791585AB32727230000
595JH55656614315851434183AF02124240000
621JH55657347858404788708GQ28133850000

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