Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Could the dash "-" be included?

From: joernbs <joern(dot)jaenecke(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Could the dash "-" be included?
Date: 2018-10-27 16:07:50
Message-ID: CAHqoMn-m0xrrqqKXhmAjZGo=W1jVzLGpuDnaiS0kuSfDAXS1CA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Dear friends,

I would like to use ltree for search paths in a warehouse application,
something like "Material-Entry-01.Main-Aisle.Shelf-Aisle-R07/R08.R07-12-03"
Unfortunately I can not use common separators like dash (-) or slash(/)

Documentation states only thes characters [A-Za-z0-9_] are allowed.
https://www.postgresql.org/docs/10/static/ltree.html

As far as I can see this limitation is set in source code of ltree, line 83:
https://doxygen.postgresql.org/ltree_8h_source.html
#define ISALNUM(x) ( t_isalpha(x) || t_isdigit(x) || ( pg_mblen(x) == 1 &&
t_iseq((x), '_') ) )

I would appreciate if at least the dash (-) and perhaps also the slash(/)
would be included to the list of allowed characters.

It is not only me, also other users are interested in this feature, some of
them even changed the source code themselves to recompile their own
Postgresql version..
https://stackoverflow.com/questions/29887093/valid-characters-in-postgres-ltree-label-in-utf8-charset/34057357

best regards

Jörn Jaenecke

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2018-10-27 16:14:43 Re: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Could the dash "-" be included?
Previous Message GPT 2018-10-27 15:00:44 Re: rw_redis_fdw: SQL Errors when statement is within a function

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2018-10-27 16:12:12 Re: Resetting PGPROC atomics in ProcessInit()
Previous Message Dmitry Molotkov 2018-10-27 15:39:33 Re: BUG #15446: Crash on ALTER TABLE