From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Poul Jensen <flyvholm(at)gfy(dot)ku(dot)dk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SQL - planet redundant data |
Date: | 2005-09-09 04:27:48 |
Message-ID: | 20050909042748.GA2470@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Sep 08, 2005 at 19:58:55 -0800,
Poul Jensen <flyvholm(at)gfy(dot)ku(dot)dk> wrote:
>
> This novice must be missing a sneaky way to avoid massive redundancy and
> still maintain easy access. I've been suggested to look at inheritance
> and foreign keys. Foreign keys I don't see how to use, but I could make
> an inheritance hierarchy of the split up tables to make the parent table
> columns (mn,tmp,wind in above example) available across tables. But
> accessing the rest of the columns still require child-table specific
> queries, and my many child tables will not be nicely nested as in above
> example, so I still don't see how it can get me there. I could really
> use some input.
You can also use views. Updatable views can be created using the rule system
if you need them.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-09 04:41:17 | Re: SQL - planet redundant data |
Previous Message | Poul Jensen | 2005-09-09 03:58:55 | SQL - planet redundant data |