Skip site navigation (1) Skip section navigation (2)

[RFC] Localized literals

From: Zoltan Boszormenyi <zb(at)cybertec(dot)at>
To: PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: [RFC] Localized literals
Date: 2008-04-23 08:02:37
Message-ID: 480EED1D.4040208@cybertec.at (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

we have a customer who shot themselves in the foot by using
table names with german accented characters in them.
The client application on the popular OS is using a single-byte
encoding (LATIN9), their dump of the original database is using
the same but no "SET client_encoding = ..." line anywhere.
We didn't know the previous conditions and have setup the
default installed database cluster that was created during installation
on Debian 4.0. Obviously we have to re-initialize the cluster
with the original locale so the table names come out right after
reloading the dump.

But the question popped up whether PostgreSQL can be extended
to allow localized literals and apply encoding conversion the same
way as on string data. NAMEDATA can be replaced with regular TEXT
and have the same conversion everywhere. This way the relation and
field name limits are also eliminated. The conversion could be controlled
by a compile-time option and/or a GUC variable. Tell me if I am crazy.

Best regards,
Zoltán Böszörményi

-- 
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/



Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2008-04-23 08:46:45
Subject: Re: [RFC] Localized literals
Previous:From: Gurjeet SinghDate: 2008-04-23 06:34:02
Subject: Re: RECORD.* doesn't work in Pl/PGSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group