> On 25 Nov 2014, at 22:24, Tom Lane <t...@sss.pgh.pa.us> wrote: > > Alban Hertroys <haram...@gmail.com> writes: >> In the past, when writing trigger functions, I’ve always used pl/pgsql >> without giving it a second thought. Today I was modifying a database >> creation script that was originally intended for Firebird to work with >> Postgres and the example trigger procedures in there were very close to pure >> SQL. > >> Hence, I started rewriting them as SQL functions, but is that really >> possible? > > No, nobody's ever tried to make that work. It could probably be done > with sufficiently many round tuits, but it's not clear that there's > any benefit that would justify the work. Surely dropping some SQL > commands into plpgsql isn't very hard …
It isn’t. I was just wondering whether I was missing something obvious to make an SQL function return a trigger type value. I didn’t think there was, but it never hurts to ask ;) Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll find there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
