On Oct 6, 2008, at 5:53 PM, Tom Lane wrote:
Ben Chobot <[EMAIL PROTECTED]> writes:
Say I have:
create t (c1 int not null, c2 int);
Is it possible to create an update trigger on t such updates will
only
be allowed if the update statement explicitly sets c1, even if the
new
value is the same?
No. A trigger can only tell whether the old and new values are the
same
or not, not why they are that way.
OK, well, that makes sense.
Is there a way I could do this with rules instead? I was thinking to
maybe have a rule to set c1 to be null on update to t, and then let
the normal update happen, and then let the not null constraint kick in
if it needs to. But when I tried to implement this idea with my
limited understanding of rules, it led to infinite recursion. :(
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
