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

From: Richard Huxton <dev(at)archonet(dot)com>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl
Date: 2010-02-15 10:42:15
Message-ID: 4B792507.8050507@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15/02/10 10:32, Tim Bunce wrote:
> On Mon, Feb 15, 2010 at 07:31:14AM +0000, Richard Huxton wrote:
>>
>> Is there any value in having a two-stage interface?
>>
>> $seq_fn = get_call('nextval(regclass)');
>> $foo1 = $seq_fn->($seq1);
>> $foo2 = $seq_fn->($seq2);
>
> I don't think there's significant performance value in that.
>
> Perhaps it could be useful to be able to pre-curry a call and
> then pass that code ref around, but you can do that trivially
> already:
>
> $nextval_fn = sub { call('nextval(regclass)', @_) };
> $val = $nextval_fn->($seq1);
> or
> $nextfoo_fn = sub { call('nextval(regclass)', 'foo_seqn') };
> $val = $nextfoo_fn->();

Fair enough. Just wondered whether it was worth putting that on your
side of the interface. I'm forced to concede you probably have more
experience in database-related APIs than me :-)

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2010-02-15 10:43:36 Re: idle in txn query cancellation
Previous Message Andres Freund 2010-02-15 10:38:06 Re: idle in txn query cancellation