| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "zengman(at)halodbtech(dot)com" <zengman(at)halodbtech(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ |
| Date: | 2024-09-25 14:51:24 |
| Message-ID: | 3647705.1727275884@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Wednesday, September 25, 2024, PG Bug reporting form <
> noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 曾满 | 2024-09-25 15:10:44 | Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ |
| Previous Message | Tom Lane | 2024-09-25 14:41:07 | Re: BUG #18097: Immutable expression not allowed in generated at |