On Thu, Aug 11, 2011 at 11:43 PM, Josh Kupershmidt <schmi...@gmail.com> wrote: > 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?
Uh, wow. That syntax is horribly surprising, isn't it? My eyes want to parse it as: BEFORE (UPDATE OF raster) OR (DELETE ON image) ...which is totally wrong. I'm inclined to think that maybe we should leave that example as-is, and maybe add the variant you're proposing as a second example, showing how the basic version can be refined. > 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. Patch? :-) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
