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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Rajanikant Chirmade <rajanikant(dot)chirmade(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: multibyte-character aware support for function "downcase_truncate_identifier()"
Date: 2010-11-23 17:51:55
Message-ID: 12028.1290534715@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-23 18:18:48 Re: SQL/MED estimated time of arrival?
Previous Message Greg Stark 2010-11-23 17:46:56 Re: multibyte-character aware support for function "downcase_truncate_identifier()"