Re: RFC: array literal syntax

I would consider that to be a bug if it would be possible to
use this as a method of compromising the integrity or security
of the database, or system using or running the database.
Otherwise it could be considered a "feature" that makes
allowances for poor software design. I would prefer it to
be considered a bug, but that is just my opinion. I prefer
software to act in a predictable way and generate errors
when deviation is attempted.

Joe Conway wrote:

> In Postgres 7.4 and earlier you can do the following:
>
> select '{{"1 2" x},{3}}'::text[];
>       text
> -----------------
>  {{"1 2 x"},{3}}
> (1 row)
>
> I regard this as a bug, and am contemplating commiting a fix this
> weekend against 8.0devel. However it was brought up on HACKERS that
> since this has always been allowed, it might be viewed by some as a
> feature, not a bug. With the proposed change, it would look like this:
>
> select '{{"1 2" x},{3}}'::text[];
> ERROR:  malformed array literal: "{{"1 2" x},{3}}"
>
> Any comments for or against calling this a bug? Now's the time to
> speak up, particularly if you depend on this as a feature.
>
> Thanks,
>
> Joe
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faqs/FAQ.html
>
> .
>

--
Guy Fraser
Network Administrator
The Internet Centre
780-450-6787 , 1-888-450-6787

There is a fine line between genius and lunacy, fear not, walk the
line with pride. Not all things will end up as you wanted, but you
will certainly discover things the meek and timid will miss out on.