| From: | "Laurent Wandrebeck" <l(dot)wandrebeck(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Column level triggers |
| Date: | 2008-10-15 08:21:35 |
| Message-ID: | fc593b510810150121ob4891abs9b288ac43764f8d7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hi,
According to the documentation (
http://www.postgresql.org/docs/8.3/interactive/sql-createtrigger.html
), the feaure "SQL allows triggers to fire on updates to specific
columns (e.g., AFTER UPDATE OF col1, col2)" is missing.
After a bit of research, I found that this feature was in the TODO
list ( http://wiki.postgresql.org/wiki/Todo#Triggers ), and that a
patch was proposed on 2005/07.
Is it going to be implemented soon ? It would greatly help, IMHO, for
load, and simplify the write of plpgsql functions called by before
triggers.
Regards, and keep up the good work, that DBMS (mostly;) rocks !
Laurent
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Vanderborght | 2008-10-15 09:03:59 | Querying on partitioned tables |
| Previous Message | Laurent Wandrebeck | 2008-10-15 08:19:59 | Re: Column level triggers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-10-15 08:22:50 | Re: Bogus attribute-number range checks in spi.c |
| Previous Message | Laurent Wandrebeck | 2008-10-15 08:19:59 | Re: Column level triggers |