Horton
Menu

Re: multibyte-character aware support for function "downcase_truncate_identifier()"

Greg Stark <gsstark@mit.edu>

View thread
From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Rajanikant Chirmade <rajanikant.chirmade@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2010-11-23T16:14:13Z
Lists: pgsql-hackers 
On Mon, Nov 22, 2010 at 12:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> No, especially if it results in queries that used to work breaking,
>> which it well could.  But I'm not sure where to go with it from there,
>> beyond throwing up my hands.
>
> Well, that's why there's been no movement on this since 2004 :-(.  The
> amount of work needed for a better solution seems far out of proportion
> to the benefits.

We could extend the existing logic to handle multi-bytes characters
though, couldn't we? It's not going to fix all the problems but at
least it'll do something sane.




-- 
greg

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Implement a solution to the 'Turkish locale downcases I incorrectly'