| From: | neilc(at)svr1(dot)postgresql(dot)org (Neil Conway) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Create separate ON INSERT and ON UPDATE triggers on tables with |
| Date: | 2005-05-30 06:52:38 |
| Message-ID: | 20050530065238.6A85F528FE@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Create separate ON INSERT and ON UPDATE triggers on tables with foreign
keys, rather than a single trigger for both events. This should not change
functionality, but it is more consistent: previously, there were trigger
functions for both "check_insert" and "check_update", but the former was
used for both events.
Bump catalog version number (not strictly necessary, but best to be
cautious).
Modified Files:
--------------
pgsql/src/backend/commands:
tablecmds.c (r1.157 -> r1.158)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablecmds.c.diff?r1=1.157&r2=1.158)
pgsql/src/include/catalog:
catversion.h (r1.270 -> r1.271)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.270&r2=1.271)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2005-05-30 07:20:59 | pgsql: When enqueueing after-row triggers for updates of a table with a |
| Previous Message | Eve W. Knapp | 2005-05-30 06:17:30 | Want something extra in bed? |