Schema for mrnaOrientInfo
  Database: susScr2    Primary Table: mrnaOrientInfo    Row Count: 41,323   Data last updated: 2020-09-01
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 365406int(10) unsigned range Start position in chromosome
chromEnd 366724int(10) unsigned range End position in chromosome
name AK395166varchar(255) values Accession of EST
intronOrientation 0smallint(6) range Orientation of introns with respect to EST
sizePolyA 23smallint(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)
      susScr2.all_mrna.qName (via mrnaOrientInfo.name)

Sample Rows
 
binchromchromStartchromEndnameintronOrientationsizePolyArevSizePolyAsignalPosrevSignalPos
587chr1365406366724AK395166023000
587chr1373106389814AK34636210330570
587chr1373116389816AK39624210150410
587chr1377217389809AK3476798170360
587chr1388820391507AK3921541170420
587chr1388823391515AK2362661160380
589chr1628583631275AK2362661160380
589chr1628591631277AK3921541180420
589chr1630282647177AK39624210150410
589chr1630284647187AK34636210330570

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