| From: | David Wheeler <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Rob Butler <crodster2k(at)Yahoo(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DO INSTEAD and conditional rules |
| Date: | 2005-04-26 20:17:26 |
| Message-ID: | 4653bc751db85ba555b1f34dfc9dbe41@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 26, 2005, at 12:35 PM, Tom Lane wrote:
> One possibility for an alternative mechanism is to allow triggers on
> views --- but I'm not sure exactly how this would work, or if it would
> solve all the problems. At the very least it would answer the "data
> stability" issue, since I suppose the trigger would receive precomputed
> rows that wouldn't change while it executed.
FWIW, SQLite allows triggers on views. They work very much like Pg's
rules (only I think that its INSTEAD OF syntax short-circuits the
execution of other triggers) in that it allows you to use a series of
SQL statements that will be executed--no function definition required.
http://www.sqlite.org/lang_createtrigger.html
Works great!
Cheers,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wheeler | 2005-04-26 20:19:42 | Re: DO INSTEAD and conditional rules |
| Previous Message | Tom Lane | 2005-04-26 19:35:32 | Re: DO INSTEAD and conditional rules |