| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ian Harding <ianh(at)tpchd(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can't use subselect in check constraint |
| Date: | 2001-12-20 21:38:39 |
| Message-ID: | 20011220133458.C82911-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 19 Dec 2001, Tom Lane wrote:
> "Ian Harding" <ianh(at)tpchd(dot)org> writes:
> > Is this something that will change anytime soon?
>
> It's not high-priority in my mind. The difficulty is the lack of a
> planning step for constraint expressions. Maybe we could fix this
> when we redesign querytrees; right now I think there's too much cruft
> in the way (memory leaks, state kept in the querytree, etc etc)
Also, AFAICS, check constraints with subselects are constraints on the
other tables named in the subselect as well and it could be on a
case which the current check constraints don't fire (for example
on delete from a table where a set value function is used, like
check (select count(*) from foo)>col1) or something like that).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Wood | 2001-12-20 21:46:29 | Re: Can't use subselect in check constraint |
| Previous Message | Peter E. Chen | 2001-12-20 21:34:52 | template question . . . |