From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Command Triggers, patch v11 |
Date: | 2012-02-27 19:31:45 |
Message-ID: | m2ipis2hum.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thom Brown <thom(at)linux(dot)com> writes:
> I've got a question regarding the function signatures required for
> command triggers, and apologies if it's already been discussed to
> death (I didn't see all the original conversations around this).
> These differ from regular trigger functions which don't require any
> arguments, and instead use special variables. Why aren't we doing the
> same for command triggers? So instead of having the parameters
Basically so that we don't have to special code support for each and
every language out there.
> Disadvantages are that there's more maintenance overhead for
> supporting multiple languages using special variables.
Lots of, so I've been told, enough of it for not taking this choice
seriously. I'll admit I didn't personally looked at what it would
entail implementation wise.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-02-27 19:37:09 | Re: Command Triggers, patch v11 |
Previous Message | Thom Brown | 2012-02-27 19:30:31 | Re: Command Triggers, patch v11 |