From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Rules: A Modest Proposal |
Date: | 2009-10-05 12:46:48 |
Message-ID: | 200910051246.n95CkmC12734@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Sabino Mullane wrote:
> Could this be done with a trigger? Yes, but on the plus rules side:
>
> * It's faster
> * It's easier to write
> * It's immediately viewable as to what is going on with a \d mytable
> * Dropping it won't leave an unused function around
> * We can still do ALTER TABLE DISABLE TRIGGER ALL
>
> I can give more examples, if you like, but removing a major feature of
> Postgres with no real justificatgion seems a bit hasty, to say the least.
Agreed, here is another rules example that logs table changes to a log
table:
http://www.postgresql.org/files/documentation/books/aw_pgsql/node124.html
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2009-10-05 13:23:28 | Re: Review of "SQLDA support for ECPG" |
Previous Message | Greg Sabino Mullane | 2009-10-05 12:30:57 | Re: Rules: A Modest Proposal |