Coverage table and exons
I am working on a NGS database and I found a problem to create the table for coverage data. Each row is a contains an interval of the entire exome sequenced. In some cases, there are multiple transcripts per interval. For this reason, I created an extra table to collect all the NMs ids.
The problem I found is related to the exons because in most cases there is more than one exon and they are separated by commas, for example: "1, 2, 3". As the exons are represented as numbers, creating an extra table is a nonsense and using ENUM is not an option. I think the best solution is consider the field as text but, is it correct?
• 1,076 views
•
link
written
by
Swimming bird •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Creating frequency table from CD-HIT output in Python
written by Paula •
-
Parsing through VCF annotated by Funcotator
written by abbysue •
-
Coverage table and exons (MySQL)
written by Swimming bird •
-
N:M or 1:M relationship?
written by Swimming bird •
-
Constructing a database for NGS data
written by Swimming bird •
-
Filtering GO terms by neuromuscular processes
written by Swimming bird •
-
Disease gene prioritization tool using protein-protein interaction network
written by Swimming bird •
-
How to get the no-overlapping exome region (.bed file)?
written by weiyuchung •
-
How To Create A .Bed File With A Few Candidate Genes?
written by newDNASeqer
-
Intersect Gene Annotation With Specific Position Or Genomic Interval
written by Nicolas Rosewick
