Re: [PATCH] Expand character set for ltree labels

2023-01-03 Thread Garen Torikian
Sure. Rebased onto HEAD. On Tue, Jan 3, 2023 at 7:27 AM vignesh C wrote: > On Thu, 6 Oct 2022 at 03:35, Garen Torikian wrote: > > > > After digging into it, you are completely correct. I had to do a bit > more reading to understand the relationships between UTF-8 and wchar

[PATCH] Expand character set for ltree labels

2022-10-04 Thread Garen Torikian
Dear hackers, I am submitting a patch to expand the label requirements for ltree. The current format is restricted to alphanumeric characters, plus _. Unfortunately, for non-English labels, this set is insufficient. Rather than figure out how to expand this set to include characters beyond the AS

Re: [PATCH] Expand character set for ltree labels

2022-10-04 Thread Garen Torikian
32 PM Nathan Bossart wrote: > On Tue, Oct 04, 2022 at 12:54:46PM -0400, Garen Torikian wrote: > > The punycode range of characters is the exact same set as the existing > > ltree range, with the addition of a hyphen (-). Within this system, any > > human language can be en

Re: [PATCH] Expand character set for ltree labels

2022-10-05 Thread Garen Torikian
ed it. > That seems really pretty random. Ok. I am trying to avoid a situation where other users may wish to use other delimiters other than `-`, due to its commonplace presence in words (eg., compound ones). On Wed, Oct 5, 2022 at 2:59 PM Tom Lane wrote: > Garen Torikian writes: > >

Re: [PATCH] Expand character set for ltree labels

2022-10-05 Thread Garen Torikian
ane wrote: > Garen Torikian writes: > >> Perhaps the docs are a bit unclear about that, but it's not > >> restricted to ASCII alphanumerics. AFAICS the code will accept > >> whatever iswalpha() and iswdigit() will accept in the database's > >> de