Re: TODO: trigger features

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: trigger features
Date: 2003-08-05 22:41:37
Message-ID: 13798.1060123297@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andreas Pflug <pgadmin(at)pse-consulting(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-08-05 22:47:56 Re: Adjustment of spinlock sleep delays
Previous Message Dave Tenny 2003-08-05 22:40:40 PostgreSQL JDBC driver Connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE) failures