templates, encoding
My template0 and template1 have SQL ASCII encoding, while I created a database with UNICODE encoding.
Could it cause some conflicts ? If so, how can I change templates databases to be UNICODE as well ?
=?iso-8859-2?Q?Zlatko_Mati=E6?= <zlatko.matic1@sb.t-com.hr> writes:
My template0 and template1 have SQL ASCII encoding, while I created a =
database with UNICODE encoding.
Could it cause some conflicts ? If so, how can I change templates =
databases to be UNICODE as well ?
The real question is whether the database's locale setting is compatible
with Unicode (utf-8). If not, you're going to see some problems with
comparing and sorting non-ASCII characters.
initdb is the only way to fix a bad choice of locale, unfortunately.
regards, tom lane
Why there is no Unicode as option during initdb. There are some encodings,
but not all alisted in PostgreSQL manual ? How different SQL ASCII is from
Unicode ?
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Zlatko Matiďż˝" <zlatko.matic1@sb.t-com.hr>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, July 29, 2005 4:21 PM
Subject: Re: [GENERAL] templates, encoding
Show quoted text
=?iso-8859-2?Q?Zlatko_Mati=E6?= <zlatko.matic1@sb.t-com.hr> writes:
My template0 and template1 have SQL ASCII encoding, while I created a =
database with UNICODE encoding.
Could it cause some conflicts ? If so, how can I change templates =
databases to be UNICODE as well ?The real question is whether the database's locale setting is compatible
with Unicode (utf-8). If not, you're going to see some problems with
comparing and sorting non-ASCII characters.initdb is the only way to fix a bad choice of locale, unfortunately.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster