Skip site navigation (1) Skip section navigation (2)

Re: Command Triggers, patch v11

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: (view raw, whole thread or download thread mbox)
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.

Dimitri Fontaine     PostgreSQL : Expertise, Formation et Support

In response to


pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2012-02-27 19:37:09
Subject: Re: Command Triggers, patch v11
Previous:From: Thom BrownDate: 2012-02-27 19:30:31
Subject: Re: Command Triggers, patch v11

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group