On Fri, Jul 03, 2009 at 05:37:20PM -0700, Reece Hart wrote:
> On Fri, 2009-07-03 at 11:29 -0700, David Fetter wrote:
>
> > I'm missing what you're doing here that foreign keys don't cover.
> > Could you send along your DDL?
>
> No DDL yet... I'm just in the thinking stages. FKs technically would
On Fri, 2009-07-03 at 11:29 -0700, David Fetter wrote:
> I'm missing what you're doing here that foreign keys don't cover.
> Could you send along your DDL?
No DDL yet... I'm just in the thinking stages. FKs technically would do
it, but would become unwieldy. The intention was to have subclasses o
On Thu, 2009-07-02 at 19:19 -0700, Nathan Boley wrote:
> Is an association, for example, an experiment that establishes a
> dependent relationship? So could there be multiple associations
> between variant and phenotype?
Exactly. You might have one group say that allele X "causes" some trait,
whe
On Thu, Jul 02, 2009 at 01:54:04PM -0700, Reece Hart wrote:
> This is a question about data modeling with inheritance and a way to
> circumvent the limitation that primary keys are not inherited.
I'm missing what you're doing here that foreign keys don't cover.
Could you send along your DDL?
Just
>
> variant association phenotype
> --- --- -
> variant_id - variant_id +--- phenotype_id
> genome_id phenotype_id -+ short_descr
> strand origin_id (i.e., who)
This is a question about data modeling with inheritance and a way to
circumvent the limitation that primary keys are not inherited.
I'm considering a project to model genomic variants and their associated
phenotypes. (Phenotype is a description of the observable trait, such as
disease or hair colo
