| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Keary Suska <hierophant(at)pcisys(dot)net> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Column 'CHECK' Constraint: bug or ? |
| Date: | 2001-09-20 05:21:16 |
| Message-ID: | Pine.BSF.4.21.0109192216350.71501-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 19 Sep 2001, Keary Suska wrote:
> It appears that Postgres checks column CHECK constraints when performing an
> update regardless of whether the particular column is being updated. Perhaps
> my understanding of column vs table constraints is incomplete but this
> doesn't seem to be proper behavior, and I can't find it documented anywhere.
If I read spec correctly, a column check constraint is equivalent to a
table constraint of the same search condition (and name and
attributes) for purposes of checking the constraint which means it should
be valid at end of transaction/statement depending on the constraint
attributes (and we don't support deferred check right now).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keary Suska | 2001-09-20 05:24:03 | Re: Column 'CHECK' Constraint: bug or ? |
| Previous Message | Tom Lane | 2001-09-20 04:02:31 | Re: Column 'CHECK' Constraint: bug or ? |