Re: Allowing dash character in LTREE

From: Cyril Auburtin <cyril(dot)auburtin(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allowing dash character in LTREE
Date: 2017-05-20 18:26:00
Message-ID: CAKteAhHJavQn7pQuWE-_0bOy7bkjbO3V093NfR2gpDNtkz8CCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ah sorry, first time, I thought it didn't pass

It's to support multiple ids (base64 ones are frequent) (or uuid's) in a
path. I think it's more practical than an array, for searching and sorting

But I understand that LTREE's main purpose is probably more for words
'breadcrumbs' etc..

2017-05-20 18:31 GMT+02:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:

> On Sat, May 20, 2017 at 1:27 AM, Cyril Auburtin <cyril(dot)auburtin(at)gmail(dot)com>
> wrote:
>
>> It could be useful to allow the `-` char in allowed LTREE label
>> characters (currently a-zA-Z0-9_ https://www.postgre
>> sql.org/docs/9.6/static/ltree.html)
>>
>> The reason is to allow to use more easily base64 ids, (like
>> https://github.com/dylang/shortid, ...), uuid's too in labels
>>
>> `-` is also not used as a query operator as a plus
>>
>>
>> source: https://doxygen.postgresql.org/ltree_8h.html#a1cb5d5
>> dd0c364d720854e8a250967dd1
>>
>
> ​This is the third time you've posted this suggestion. Its been seen by
> the people you are sending it to.
>
> I don't follow how this helps for UUID - they are not usually generated
> hierarchically​...
>
> I'll +1 the thought, but I won't be providing a patch.
>
> David J.
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2017-05-20 18:51:54 Re: Allowing dash character in LTREE
Previous Message Pavel Stehule 2017-05-20 17:58:57 Re: proposal psql \gdesc