Is TG_NARGS/TG_ARGV just legacy, or what? - Mailing list pgsql-hackers

From Josh Berkus
Subject Is TG_NARGS/TG_ARGV just legacy, or what?
Date
Msg-id 200603041444.04650.josh@agliodbs.com
Whole thread Raw
Responses Re: Is TG_NARGS/TG_ARGV just legacy, or what?
List pgsql-hackers
Folks,

I was just building something and noticing the peculiar structure we've 
given to arguments to trigger procedures.  Instead of declaring them 
normally, we pass them through the variables TG_NARGS and TG_ARGV[].  This 
is inconsistent with the entire rest of Postgres, as well as making it 
hard to validate passed constants (e.g. if you pass the wrong number of 
arguments, you won't know it until execution time).

Is there some sound technical reason not to use the standard argument 
declaration, or is this just something we've overlooked fixing?

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Not so happy with psql's new multiline behavior
Next
From: "Andrew Dunstan"
Date:
Subject: Re: Is TG_NARGS/TG_ARGV just legacy, or what?