| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "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 12:33:15 |
| Message-ID: | CAKFQuwb2F8Pnw8+Ftb=5zerGGO7sG2-p=cVGsY9=p3ZWVXxmVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, September 25, 2024, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18632
> Logged by: Man Zeng
> Email address: zengman(at)halodbtech(dot)com
> PostgreSQL version: 14.10
> Operating system: centos-8
> Description:
>
> Hi, I found a problem with array separator handling.
> The current handling of delimiters is not quite as expected (not very
> flexible).
>
> 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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 曾满 | 2024-09-25 12:45:17 | Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ |
| Previous Message | Adrien Nayrat | 2024-09-25 11:07:13 | Re: BUG #18097: Immutable expression not allowed in generated at |