On Thu, Sep 08, 2005 at 19:58:55 -0800,
Poul Jensen <flyvholm@gfy.ku.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.
