Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Robert Haas <robertmhaas@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Rajanikant Chirmade <rajanikant.chirmade@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2010-11-23T17:51:55Z
Lists: pgsql-hackers 
Greg Stark <gsstark@mit.edu> writes:
> I'm not sure I understand the danger if a user creates an object in a
> database with a particular encoding and locale using that locale for
> downcasing in the future.

The case I was worried about is dumping from one database and reloading
into another one with a different locale.  Although I suppose there are
enough *other* reasons why that might fail that adding changes of
downcasing behavior might not be a big deal.

			regards, tom lane

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'