From: | joernbs <joern(dot)jaenecke(at)gmail(dot)com> |
---|---|
To: | david(dot)g(dot)johnston(at)gmail(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Ltree: set of allowed charcters is limited to [A-Za-z0-9_]. Could the dash "-" be included? |
Date: | 2018-10-28 09:31:32 |
Message-ID: | CAHqoMn_BQPX-jZs21W-T1=f1aJKQmios2f61+LdZ0kyRU+W-BA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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(dot)g(dot)johnston(at)gmail(dot)com>:
> On Saturday, October 27, 2018, joernbs <joern(dot)jaenecke(at)gmail(dot)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.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2018-10-28 12:44:18 | Re: Enabling bdr in multiple databases on the same postgresql instance/cluster |
Previous Message | Christoph Moench-Tegeder | 2018-10-27 22:13:22 | Re: rw_redis_fdw: SQL Errors when statement is within a function |
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2018-10-28 11:35:36 | Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? |
Previous Message | Fabien COELHO | 2018-10-28 06:54:53 | Re: Conflicting option checking in pg_restore |