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 <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
