From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | lo_manage trigger on updates |
Date: | 2011-08-12 03:43:47 |
Message-ID: | CAK3UJRHaEuzfnZaxarcV8=RP1sC5xLxumzqx6iiyqpJVS89rjw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hi all,
I think the doc section about using lo_manage() as a trigger:
http://www.postgresql.org/docs/current/static/lo.html
could have its example tweaked to use a column-level BEFORE UPDATE
trigger, so as to save unnecessary trigger firings. Something like the
attached, perhaps?
On a similar note, the warning on that page about truncates could be
softened if we extended the lo_manage() function to handle truncates,
and set it up as on ON TRUNCATE trigger as well.
Josh
Attachment | Content-Type | Size |
---|---|---|
lo.diff | application/octet-stream | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-08-15 16:58:00 | Foreign server version and type |
Previous Message | Alvaro Herrera | 2011-08-11 17:47:41 | Re: DOCUMENTATION IN OTHERS IDIOMS |