From: | Zlatko Matić <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: templates, encoding |
Date: | 2005-07-31 05:17:41 |
Message-ID: | 003701c5958f$2dc786c0$97301dc3@zlatkovyfkpgz6 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)sss(dot)pgh(dot)pa(dot)us>
To: "Zlatko Matić" <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Friday, July 29, 2005 4:21 PM
Subject: Re: [GENERAL] templates, encoding
> =?iso-8859-2?Q?Zlatko_Mati=E6?= <zlatko(dot)matic1(at)sb(dot)t-com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey Melloy | 2005-07-31 05:54:09 | Re: Tool for database design documentation? |
Previous Message | Brock Williams | 2005-07-30 22:02:11 | FATAL: cache lookup failed for access method 6881280 |