From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: arrays as pl/perl input arguments [PATCH] |
Date: | 2011-01-11 23:07:53 |
Message-ID: | 5E1F901A-E1A3-4BF9-8AE7-20128503FB6C@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 11, 2011, at 2:25 PM, Alexey Klyukin wrote:
> Hello,
>
> Here's the patch that improves handling of arrays as pl/perl function input
> arguments, converting postgres arrays of arbitrary dimensions into perl array
> references.
Awesome! I've wanted this for *years*.
> It includes regression tests and a documentation changes, and it
> builds and runs successfully on my mac os x and linux boxes. To maintain
> compatibility with existing pl/perl code a new variable,
> plperl.convert_array_arguments (better name?), is introduced. Its default
> value is false, when set to true it triggers the new behavior, i.e.
Have you considered instead passing an array-based object with is string overloading designed to return the pg array string format? That would make for nice, transparent compatibility without the need for a GUC.
Not my idea, BTW, but suggested by Tim Bunce.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2011-01-11 23:23:38 | Re: Allowing multiple concurrent base backups |
Previous Message | Peter Eisentraut | 2011-01-11 23:06:58 | pg_regress multibyte setting |