From: | "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Postgresql inheritance workaround |
Date: | 2005-02-24 14:11:19 |
Message-ID: | 6C0CF58A187DA5479245E0830AF84F4208053A@poweredge.attiksystem.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi,
Because of the actual limitations of Postgresql inheritance mecanism
regarding constraints, I'm not willing to use it in my project, although
it's exactly the kind of idea I need:
In an order and manufacturing management system, several different items
can be ordered, each of them with specific input parameters.
Every item has its own table of "specific parameters", now, what is the
best use of PK/FK in order to maintain integrity between the order lines
and the items specific parameters tables?
Has anyone already done that before?
Thanks for your help, and for Posgresql by the way, which is really
great...
----------------------------------
Philippe Lang
Attik System
From | Date | Subject | |
---|---|---|---|
Next Message | Przemyslaw Slupkowski | 2005-02-24 14:20:48 | Re: Software for database-visualisation |
Previous Message | Joel Fradkin | 2005-02-24 13:51:38 | Re: Speeds using a transaction vrs not |