From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: martin@schlossarek.me
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18057: unaccent removes intentional spaces
Date: Sun, 20 Aug 2023 09:20:48 +0900
Message-ID: <ZOFcYPLTTFvKpZMi@paquier.xyz> (raw)
In-Reply-To: <2399066.1692490106@sss.pgh.pa.us>
References: <18057-62712cad01bd202c@postgresql.org>
<ZNwRq4nV7CBXAoJN@paquier.xyz>
<ZN8NUpx2f9pB+F/g@paquier.xyz>
<2334732.1692462604@sss.pgh.pa.us>
<ZOFW6ZBerH/IBoTC@paquier.xyz>
<2399066.1692490106@sss.pgh.pa.us>
On Sat, Aug 19, 2023 at 08:08:26PM -0400, Tom Lane wrote:
> I was envisioning following SQL identifier rules, that is you double
> the double quote. Then the existing " entries would have to become
> """", which isn't much fun. But what you're suggesting would make
> both " and \ into magic characters, doubling the chance of problems
> with existing rules files.
Apologies for the confusion. I was thinking to also escape \ in
quoted strings. Your suggestion to use a second double-quote for the
escaping is fine by me. """" feels a bit ugly-ish in the rules file,
for sure, but that does not look like a huge issue to me as long as
the python script generates consistent contents ;)
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: michael@paquier.xyz, tgl@sss.pgh.pa.us, martin@schlossarek.me, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18057: unaccent removes intentional spaces
In-Reply-To: <ZOFcYPLTTFvKpZMi@paquier.xyz>
* 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