Re: abnormal behaviour of a CHECK CONSTRAINT with a regular expression when a trigger is added

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Struck <struck(dot)d(at)retrovirology(dot)lu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: abnormal behaviour of a CHECK CONSTRAINT with a regular expression when a trigger is added
Date: 2004-02-10 16:23:15
Message-ID: 15682.1076430195@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Daniel Struck <struck(dot)d(at)retrovirology(dot)lu> writes:
> This makes it also impossible to change the type of a value by a trigger?

Correct. It is annoying in some cases, but if the input to the trigger
isn't of the column datatype, then what type is it? It's hard to see
how that could work in general.

If you want, say, a varchar length constraint to be checked only after
the trigger runs, I'd counsel declaring the column as plain text and
writing the length test as a CHECK constraint.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-02-10 22:54:33 BUG #1077: install-strip does not work for MacOS X 10.2.8
Previous Message Tom Lane 2004-02-10 16:12:39 Re: [BUGS] Probably a security bug in PostgreSQL rule system