Hi
all,
I have a
table where two columns have two different check constraints associated with
them. When I update one column, the check constraint on the other column is also
executed. Is there a way to avoid this? I want to check only for the condition
defined for the column being update
PROTECTED]
Sent: Friday, January 27, 2006 9:25 PM
To: Kashmira Patel (kupatel)
Cc: Michael Fuhr; pgsql-sql@postgresql.org
Subject: Re: [SQL] Question about check constraints
On Fri, 27 Jan 2006, Kashmira Patel (kupatel) wrote:
> Both concerns.
> 1) There are actually more than two columns wit
rcome this?
I'd second Michael's suggestion of a trigger.
> -----Original Message-----
> From: Michael Fuhr [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 27, 2006 4:40 PM
> To: Kashmira Patel (kupatel)
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] Question about
ggestions on the best way to overcome this?
Thanks,
kashmira
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Friday, January 27, 2006 4:40 PM
To: Kashmira Patel (kupatel)
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Question about check constraints
On Fri, Jan 27,
On Fri, Jan 27, 2006 at 03:06:26PM -0800, Kashmira Patel (kupatel) wrote:
> I have a table where two columns have two different check constraints
> associated with them. When I update one column, the check constraint on
> the other column is also executed. Is there a way to avoid this? I want
> t
Hi
all,
I have a
table where two columns have two different check constraints associated with
them. When I update one column, the check constraint on the other column is also
executed. Is there a way to avoid this? I want to check only for the condition
defined for the column being upd