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
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2011-01-12 21:05:12|
|Subject: Re: libpq documentation cleanups (repost 3)|
|Previous:||From: Alexey Klyukin||Date: 2011-01-12 20:13:25|
|Subject: Re: arrays as pl/perl input arguments [PATCH]|