| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David E(dot) Wheeler <david(at)kineticode(dot)com> |
| Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Alexey Klyukin <alexk(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: arrays as pl/perl input arguments [PATCH] |
| Date: | 2011-01-12 20:17:08 |
| Message-ID: | 1294863385-sup-4470@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from David E. Wheeler's message of mié ene 12 16:55:17 -0300 2011:
> On Jan 12, 2011, at 11:51 AM, Alvaro Herrera wrote:
>
> >> I suspect it'd be quiet, unfortunately, since there are a bazillion ad hoc implementations of a Perl SQL array parser, and many of them, I suspect, don't complain if the string doesn't look like an SQL array. They would just parse a string like "ARRAY(0x118ee2a0)" and return an empty array, or a NULL.
> >
> > I kinda doubt that a function failing in that way would pass any
> > testing.
>
> What is this “testing” thing of which you speak?
Ha ha ha :-(
I wonder if there's a way to overload the string representation of the
array so that it throws an error.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2011-01-12 21:05:12 | Re: libpq documentation cleanups (repost 3) |
| Previous Message | Alexey Klyukin | 2011-01-12 20:13:25 | Re: arrays as pl/perl input arguments [PATCH] |