From: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Foreign keys: unexpected result from ALTER TABLE... ADD CONSTRAINT... |
Date: | 2000-01-17 14:06:01 |
Message-ID: | 200001171406.OAA14889@linda.lfix.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>On Mon, 17 Jan 2000, Oliver Elphick wrote:
>
>> I cannot do this pair of table creations directly, because they are mutual
>ly
>> dependent.
>>
>
>I don't think this will ever work. I can't really decode your intentions
>here but I recall that translating proper relational schemas (you know,
>the ones with the bubbles and lines) into tables never creates this sort
>of situation. Then again I could be wrong.
The idea is that suppliers of products can only supply products that are
purchased, rather than manufactured; and purchased products must have
suppliers. However, it is possible for there to be more than one potential
supplier of a product; the one listed in purchased_jobs is the currently
favoured supplier.
I guess I will have to remove the restriction that products listed in
product_suppliers must be purchased; it may indeed become possible for the
to change status from time to time, so that is not too unsatisfactory.
--
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"And, behold, I come quickly; and my reward is with me,
to give every man according as his work shall be."
Revelation 22:12
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-01-17 14:06:15 | Re: [HACKERS] Auto-lowercasing of column names? |
Previous Message | Hakan Tandogan | 2000-01-17 13:45:42 | Auto-lowercasing of column names? |