From: | Miles Keaton <mileskeaton(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: brain-teaser with CONSTRAINT - any SQL experts? |
Date: | 2005-10-10 03:21:21 |
Message-ID: | 59b2d39b0510092021p776e120bubce1f591a599f0bd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Uwe said:
> how about using 2 tables with according unique/primary key constraints and a
> view to actually access the data (mixing the 2 tables into one) ?
Oliver said:
> Create a separate table with the two columns name and isbn which are
> that table's primary key; on the main table, create a foreign key to the
> new table
But my original email said:
> > I know it's tempting to say, "just link a separate table for the book
> > and don't store the book name" but let's just pretend that's not an
> > option
For reasons not worth going into, creating a separate table for the
code and name is not an option. It has to be a self-contained
restriction inside this table.
Perhaps there's another way, using triggers or something?
Any other ideas?
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Morris | 2005-10-10 03:22:33 | Re: Oracle buys Innobase |
Previous Message | CSN | 2005-10-10 02:50:39 | Re: Oracle buys Innobase |