From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: zengman@halodbtech.com <zengman@halodbtech.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？
Date: Wed, 25 Sep 2024 10:51:24 -0400
Message-ID: <3647705.1727275884@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwb2F8Pnw8+Ftb=5zerGGO7sG2-p=cVGsY9=p3ZWVXxmVA@mail.gmail.com>
References: <18632-15cedd7d4154ea2a@postgresql.org>
<CAKFQuwb2F8Pnw8+Ftb=5zerGGO7sG2-p=cVGsY9=p3ZWVXxmVA@mail.gmail.com>
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Wednesday, September 25, 2024, PG Bug reporting form <
> noreply@postgresql.org> wrote:
>> So should we consider modifying "array_in" to enhance the handling of
>> separators to be more consistent with people's expectations?
> A design being inflexible or not meeting people’s expectations is not a
> bug. The system is behaving as documented. And we are not going to be
> redefining how valid code is parsed here.
Yeah, I seriously doubt that we could change array_in's behavior
for single quotes (to wit, that they are not special in any way)
without breaking existing applications.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, zengman@halodbtech.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？
In-Reply-To: <3647705.1727275884@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox