Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> OK, attached is a file with the original function, and an overloaded one
> that just takes table and column. It searches your current search_path
> to find the first matching table.
The right way to do this at the C level would be to use the same
infrastructure as nextval() does to accept arguments like 'foo' and
'"Foo"."Bar"'. There's no reason to restrict the two-argument form
to the current search_path.
Given that you do that, I'm not sure that a three-argument form is even
needed. AFAIR no one has asked for a two-argument form of nextval...
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2004-06-12 17:50:09|
|Subject: Re: File leak? |
|Previous:||From: Stephan Szabo||Date: 2004-06-12 17:27:15|
|Subject: Re: Nested xacts: looking for testers and review|
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2004-06-12 19:30:30|
|Subject: pgsql-server: Some editorializing on 7.4.3 release notes.|
|Previous:||From: Christopher Kings-Lynne||Date: 2004-06-12 10:12:37|
|Subject: Re: [COMMITTERS] pgsql-server: Clean up generation of default|