| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SET CONSTRAINTS and like named constraints |
| Date: | 2003-09-05 00:38:51 |
| Message-ID: | 200309050038.h850cpM19547@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephan Szabo wrote:
>
> It looks like that right now if you have multiple constraints
> with the same name on different tables and some are deferrable
> and some are not, SET CONSTRAINTS "name" DEFERRED will fail when
> it reaches the not deferrable constraint. Is this the behavior
> we want, or do we want it to defer the deferrable ones with that
> name and possibly warn that some were not deferrable?
We have this TODO:
* Allow SET CONSTRAINTS to be qualified by schema/table
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-05 00:40:52 | Re: Stats Collector Error 7.4beta1 and 7.4beta2 |
| Previous Message | Tom Lane | 2003-09-05 00:38:38 | Re: Stats Collector Error 7.4beta1 and 7.4beta2 |