Re: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Couldthe dash "-" be included? - Mailing list pgsql-general

From joernbs
Subject Re: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Couldthe dash "-" be included?
Date
Msg-id CAHqoMn_BQPX-jZs21W-T1=f1aJKQmios2f61+LdZ0kyRU+W-BA@mail.gmail.com
Whole thread Raw
In response to Re: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Couldthe dash "-" be included?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general

Hello David,

I think this is a misunderstanding.
The seperator in ltree is the dot (.) , of cause I did not asked to change that.
I asked about to expand allowed characters in the ltree-string [A-Za-z0-9_] to [a-zA-Z0-9_/- ] including dash(-), slash(/) and whitespace( ), common charcaters in wording or real path-names to be transformed into and from ltree.

Jörn

Am Sa., 27. Okt. 2018 um 18:14 Uhr schrieb David G. Johnston <david.g.johnston@gmail.com>:
On Saturday, October 27, 2018, joernbs <joern.jaenecke@gmail.com> wrote:
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

I don’t see how this would be possible to do with the existing type - too much potential breakage of existing data.  Your example itself shows why using dash as a separator is a bad idea.

David J.

pgsql-general by date:

Previous
From: Christoph Moench-Tegeder
Date:
Subject: Re: rw_redis_fdw: SQL Errors when statement is within a function
Next
From: Martín Marqués
Date:
Subject: Re: Enabling bdr in multiple databases on the same postgresqlinstance/cluster