From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inconsistent results with libc sorting on Windows |
Date: | 2023-08-11 13:18:48 |
Message-ID: | 20230811131848.GA2261449@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 11, 2023 at 11:48:18AM +0200, Juan José Santamaría Flecha wrote:
> On Fri, Aug 11, 2023 at 7:29 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> >
> > The LCMapStringEx() solution is elegant. I do see
> >
> > https://learn.microsoft.com/en-us/windows/win32/intl/handling-sorting-in-your-applications
> > says, "If an application calls the function to create a sort key for a
> > string
> > containing an Arabic kashida, the function creates no sort key value."
> > That's
> > aggravating.
> >
>
> I think the problem there is that it is just poorly explained.
> Take for example the attached program that compares "normal" and "kashida"
> 'Raħīm' taken from [1], you'll get:
>
> c1 = c2
> c2 = c1
>
> meaning that "normal" and "kashida" are the same string. So, probably that
> phrase should read something like: "If an application calls the function to
> create a sort key for a string containing an Arabic kashida character, the
> function will ignore that character and no sort key value will be generated
> for it."
Good. That sounds fine. Thanks for clarifying.
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2023-08-11 13:20:52 | Re: Report planning memory in EXPLAIN ANALYZE |
Previous Message | Ashutosh Bapat | 2023-08-11 12:54:37 | Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning |