From: | Dmitry Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Natural sort order extension. |
Date: | 2020-02-12 17:14:36 |
Message-ID: | CAAfz9KN74k4fere4CEYz-i+x0fisJFYKJOq8JwoKj80=EFrpOA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 12 Feb 2020, 19:55 Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Wed, 2020-02-12 at 18:45 +0300, Dmitry Igrishin wrote:
> > I've implemented a PostgreSQL extension for natural sort order. I.e.
> > strings like "z20", "z0004", "z11", "z2" sorted in ascending order as
> > "z2", "z0004", "z11", "z20".
> >
> > Currently it implements the type textnso which is binary-coercible
> > to/from the text type. It's possible to declare table columns of type
> > textnso and create indexes on them.
> >
> > Details are here https://github.com/dmitigr/pgnso
> >
> > Any feedback are welcome!
>
> I don't want to detract from this, but from PostgreSQL v10 on you can use
> ICU collations with the "kn-true" variant to have natural sort order.
>
Thanks for the point. But my extension works with default collation and
UTF-8 encoding. And ICU is not required.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-02-12 17:23:22 | Re: Avoiding out of date statistics / planner |
Previous Message | Tom Lane | 2020-02-12 16:59:46 | Re: How to restore roles without changing postgres password |