| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
| Cc: | "Roderick A(dot) Anderson" <raanders(at)acm(dot)org>, PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Update of foreign key values |
| Date: | 2003-08-12 05:51:00 |
| Message-ID: | 20030811223845.T97310-100000@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11 Aug 2003, Ron Johnson wrote:
> On Mon, 2003-08-11 at 18:40, Roderick A. Anderson wrote:
> > On 11 Aug 2003, Ron Johnson wrote:
> >
> > > Maybe this will do it:
> > > http://www.postgresql.org/docs/7.3/static/sql-set-constraints.html
> >
> > Saw this but my take was it required the original constraint to be created
> > with the deferred(able) option. But hey, I'll give it a try since all my
>
> Where do you see that? "or INITIALLY IMMEDIATE NOT DEFERRABLE. The
> third class is not affected by the SET CONSTRAINTS command."???
Yes. Either DEFERRABLE or INITIALLY DEFERRED must be given in order for
set constraints to be meaningful. This might be another good place to
consider a little clarification (or maybe a doc note in the interactive
docs)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-08-12 07:33:14 | Re: PL/C functions |
| Previous Message | Stephan Szabo | 2003-08-12 05:38:02 | Re: types of constraint deferment |