From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | WIP: Triggers on VIEWs |
Date: | 2010-08-15 17:38:19 |
Message-ID: | AANLkTimJw47yZHnxKhMNLCFES=W-sMrqpRe7aj8YBKds@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here is a WIP patch implementing triggers on VIEWs, as outlined in the
proof-of-concept here:
http://archives.postgresql.org/pgsql-hackers/2010-08/msg00160.php
The new triggers allowed on a VIEW are:
1). Statement-level BEFORE INSERT/UPDATE/DELETE
2). Row-level INSTEAD OF INSERT/UPDATE/DELETE
3). Statement-level AFTER INSERT/UPDATE/DELETE
The new INSTEAD OF trigger type may only be used with VIEWs, and may
only be row-level. It does not support the WHEN or FOR UPDATE OF
column_list options.
There are still a number of things left todo:
- extend ALTER VIEW with enable/disable trigger commands
- much more testing
- documentation
and then there's the question of what to do about the concurrency
issues raised by Marko Tiikkaja. Currently it works like Oracle (i.e.,
no locking).
Regards,
Dean
Attachment | Content-Type | Size |
---|---|---|
view_triggers.patch | application/octet-stream | 87.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-15 18:25:03 | Re: Python 2.7 deprecated the PyCObject API? |
Previous Message | Hitoshi Harada | 2010-08-15 11:44:08 | Writeable CTEs Desgin Doc on Wiki |