From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: using Core Foundation locale functions |
Date: | 2014-12-03 06:13:08 |
Message-ID: | CAM3SWZRUcVPzeGjfuAfTCL5WPUHPPzuzeu9np4QyJe5d4p3u_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 2, 2014 at 10:07 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 12/02/2014 12:52 AM, David E. Wheeler wrote:
>> Gotta say, I’m thrilled to see movement on this front, and especially pleased to see how consensus seems to be building around an abstracted interface to keep options open. This platform-specific example really highlights the need for it (I had no idea that there was separate and more up-to-date collation support in Core Foundation than in the UNIX layer of OS X).
>
> It'd also potentially let us make use of Windows' native locale APIs,
> which AFAIK receive considerably more love on that platform than their
> POSIX back-country cousins.
Not to mention the fact that a MultiByteToWideChar() call could be
saved, and sortsupport for text would just work on Windows.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Kouhei Kaigai | 2014-12-03 06:23:28 | Re: using custom scan nodes to prototype parallel sequential scan |
Previous Message | Kouhei Kaigai | 2014-12-03 06:10:50 | Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |