Re: Is TG_NARGS/TG_ARGV just legacy, or what?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is TG_NARGS/TG_ARGV just legacy, or what?
Date: 2006-03-04 23:47:27
Message-ID: 200603041547.28145.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew,

> It does have the advantage that you can call a single trigger function
> with variable argument types/numbers. "Fixing" it would involve an
> unknown amount of legacy breakage.

Yes ... I don't see a good way to maintain legacy compatibility.

Triggers seem like the least useful place to have variable-argument
functions, though. And it is inconsistent with how we use functions
everywhere else, as well as in violation of the SQL03 standard on CREATE
FUNCTION (don't know what the standard says about triggers, though).

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-03-04 23:59:59 Re: Is TG_NARGS/TG_ARGV just legacy, or what?
Previous Message Josh Berkus 2006-03-04 22:44:04 Is TG_NARGS/TG_ARGV just legacy, or what?