| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | patrick keshishian <patrick+pgsql(at)pioneerdigital(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: re: 7.1.2 and foreign key unique constraint. |
| Date: | 2001-08-03 20:54:56 |
| Message-ID: | Pine.BSF.4.21.0108031348170.17100-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 3 Aug 2001, patrick keshishian wrote:
> Thanks for your reply and suggestions. I was hoping for a
> solution that would not require me to break apart any of the
> tables or employ new ones.
>
> But apparently i have no choice.
>
> One would think that there would a such a construct defined in
> SQL for specifying a field in a table with restriction placed on
> its values based on values in a 'foreign table field'.
Technically, you would be able to handle this through a subquery
in a check constraint, however we don't support this currently
(it's a non-trivial problem to solve for a potentially complicated
query).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Calvin Dodge | 2001-08-04 00:06:31 | Re: Where is the database located in 7.1.2? |
| Previous Message | Trond Eivind Glomsrød | 2001-08-03 20:44:41 | Re: HELP! BUG? pg_dump mucks up grant/revoke |