Schema for mrnaOrientInfo
  Database: caeRem2    Primary Table: mrnaOrientInfo    Row Count: 614   Data last updated: 2016-04-06
Format description: Extra information on ESTs - calculated by polyInfo program
On download server: MariaDB table dump directory
fieldexampleSQL type info description
bin 590smallint(5) unsigned range Indexing field to speed chromosome range queries.
chrom chrUnvarchar(255) values Reference sequence chromosome or scaffold
chromStart 669695int(10) unsigned range Start position in chromosome
chromEnd 671815int(10) unsigned range End position in chromosome
name EU183211varchar(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
        caeRem2.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
590chrUn669695671815EU18321120000
595chrUn14237741424742EU18322030000
74chrUn14410071443021DQ86889561000
596chrUn14455261447530DQ86889661000
596chrUn15392081540575EU16551630000
597chrUn16269641627692DQ06025610100
597chrUn16968031698552DQ11535560000
599chrUn19181421920751FJ80483790000
599chrUn19181421920751FJ80483890000
599chrUn19181421920751FJ80483990000

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