Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl - Mailing list pgsql-hackers

From Tim Bunce
Subject Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl
Date
Msg-id 20100218093516.GX373@timac.local
Whole thread Raw
In response to Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl
Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl
List pgsql-hackers
On Wed, Feb 17, 2010 at 10:30:03AM -0800, David E. Wheeler wrote:
> On Feb 17, 2010, at 4:28 AM, Tim Bunce wrote:
> 
> >> Yes, but if it's a variadic function, I suspect that it won't often be
> >> called with the same number of args. So you'd potentially end up
> >> caching a lot of extra stuff that would never be used again.
> > 
> > Potentially. Patches welcome!
> 
> GitHub. ;-P

http://github.com/timbunce/posgtresql-plperl-call

> > Umm, perhaps F->funcname(@args), or PG->funcname(@args), or ... ?
> > 
> > Anyone got any better suggestions?
> 
> PG is good. Or maybe DB?

On Thu, Feb 18, 2010 at 08:26:51AM +0000, Richard Huxton wrote:
> 
> It's a module whose only use is embedded in a DB called PG - not
> sure those carry any extra info. It also treads on the toes of
> "PG->not_a_function" should such a beast be needed.
> 
> I like "F->funcname" or "FN->funcname" myself.

Thanks. I quite like FN.

Anybody else want to express an opinion on the color if this bikeshed
before I repaint it?

Tim.


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: codlin_month is up and complain - PL/Python crash
Next
From: Magnus Hagander
Date:
Subject: Re: A thought: should we run pgindent now?