Re: SET CONSTRAINTS not schema-aware

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Bruno Wolff III <bruno(at)wolff(dot)to>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET CONSTRAINTS not schema-aware
Date: 2003-06-04 21:49:54
Message-ID: 200306042149.h54LnsB15903@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Peter, I assume SET CONSTRAINTS can't control a domain's constraints ---
> > it isn't actually a data object in the transaction. Am I right?
>
> No. SET CONSTRAINTS on a domain constraint should affect all constraints
> on columns that use the domain.

Oh, wow. That is interesting. Does it effect only the current
transaction? Current manual page text is:

SET CONSTRAINTS sets the behavior of constraint evaluation
in the current transaction. In IMMEDIATE mode, constraints
...

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-06-04 21:51:34 Re: default locale considered harmful? (was Re: [GENERAL]
Previous Message Carlos Guzman Alvarez 2003-06-04 21:48:50 Re: Problem trying to implement version 3.0 of the PostgreSQL