pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ 2+ messages / 1 participants [nested] [flat]
* Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ @ 2024-09-25 12:45 曾满 <zengman@halodbtech.com> 0 siblings, 0 replies; 2+ messages in thread From: 曾满 @ 2024-09-25 12:45 UTC (permalink / raw) To: David G. Johnston <david.g.johnston@gmail.com>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> Ok, you're right, there really isn't any problem from a separator point of view ----------Reply to Message---------- On Wed, Sep 25, 2024 20:33 PM David G. Johnston<david.g.johnston@gmail.com> wrote: On Wednesday, September 25, 2024, PG Bug reporting form <noreply@postgresql.org> wrote: The following bug has been logged on the website: Bug reference: 18632 Logged by: Man Zeng Email address: zengman@halodbtech.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. ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ @ 2024-09-25 15:10 曾满 <zengman@halodbtech.com> 0 siblings, 0 replies; 2+ messages in thread From: 曾满 @ 2024-09-25 15:10 UTC (permalink / raw) To: Tom Lane <tgl@sss.pgh.pa.us>; David G. Johnston <david.g.johnston@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>; david.g.johnston <david.g.johnston@gmail.com>; ewie <ewie@ewie.name>; walther <walther@technowledgy.de> Okay, thank you for your guidance, and thank you again. ----------Reply to Message---------- On Wed, Sep 25, 2024 22:51 PM Tom Lane<tgl@sss.pgh.pa.us> wrote: "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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-09-25 15:10 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-09-25 12:45 Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ 曾满 <zengman@halodbtech.com> 2024-09-25 15:10 Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters？ 曾满 <zengman@halodbtech.com>
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