Re: TODO: trigger features - Mailing list pgsql-hackers

From Tom Lane
Subject Re: TODO: trigger features
Date
Msg-id 13798.1060123297@sss.pgh.pa.us
Whole thread Raw
In response to Re: TODO: trigger features  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: TODO: trigger features
List pgsql-hackers
Andreas Pflug <pgadmin@pse-consulting.de> writes:
> I wonder why you are suggesting workarounds for features that other 
> databases provide.

The fact that other databases provide 'em doesn't make them good ideas.
In particular, writing a trigger that assumes that only the fields
changed by the original UPDATE syntax have really changed seems like an
excellent way to shoot yourself in the foot.  Why should we go out of
our way to provide support for error-prone programming techniques?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dave Tenny
Date:
Subject: PostgreSQL JDBC driver Connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE) failures
Next
From: Rod Taylor
Date:
Subject: Re: Adjustment of spinlock sleep delays