From frum@ar-sd.net Tue Apr 25 13:20:09 2006 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 326D211F65D9 for ; Tue, 25 Apr 2006 10:20:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 10427-07 for ; Tue, 25 Apr 2006 10:19:59 -0300 (ADT) X-Greylist: delayed 00:26:12.425928 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id E576C11F6260 for ; Tue, 25 Apr 2006 10:19:57 -0300 (ADT) Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by svr4.postgresql.org (Postfix) with ESMTP id C18115B1759 for ; Tue, 25 Apr 2006 12:51:34 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 494DC2D9E6 for ; Tue, 25 Apr 2006 15:51:30 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09050-01 for ; Tue, 25 Apr 2006 15:51:28 +0300 (EEST) Received: from forge (unknown [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id 782712D789 for ; Tue, 25 Apr 2006 15:51:28 +0300 (EEST) Message-ID: <027501c66866$ff0999d0$0b00a8c0@mpsro.dom> From: "Andy" To: Subject: Database LATIN1 to UFT-8 (unicode) converting problem Date: Tue, 25 Apr 2006 15:51:39 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0272_01C66880.23D3BF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/266 X-Sequence-Number: 21435 This is a multi-part message in MIME format. ------=_NextPart_000_0272_01C66880.23D3BF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi to all,=20 We just tried to switch out database from LATIN 1 (ISO 8859-1) to UTF-8. = After a few tests we found out some problems: - the upper and lower functions does not work for all characters. = Especially lower returns nothing if a umlaut is in the converted string. = The umlauts are not converted at all. - the returned rows are not correctly sorted. =F6 is before a and so on. = The server is a Suse 10 system. DB is Postgresql 8.0.3.=20 This sorting problem we had it before and it was the problem was at = local system settings. Now everything is switched to UTF-8 (or it seems = so).=20 Please advise.=20 Thank you, Andy. ------=_NextPart_000_0272_01C66880.23D3BF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi to all,
 
We just tried to switch out database = from LATIN 1=20 (ISO 8859-1) to UTF-8. After a few tests we found out some=20 problems:
 - the upper and lower functions = does not work=20 for all characters. Especially lower returns nothing if a umlaut is in = the=20 converted string. The umlauts are not converted at all.
- the returned rows are not correctly = sorted. =F6 is=20 before a and so on.
 
The server is a Suse 10 system. DB is = Postgresql=20 8.0.3.
 
This sorting problem we had it before = and it was=20 the problem was at local system settings. Now everything is switched to = UTF-8=20 (or it seems so).
 
Please advise.
 
Thank you,
Andy.
 
------=_NextPart_000_0272_01C66880.23D3BF20-- From frum@ar-sd.net Wed Apr 26 11:49:47 2006 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 308BD11F6089 for ; Wed, 26 Apr 2006 08:49:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 97661-05 for ; Wed, 26 Apr 2006 08:49:25 -0300 (ADT) X-Greylist: delayed 22:57:53.960246 by SQLgrey- Received: from ar-sd.net (mail.ar-sd.net [81.196.35.136]) by postgresql.org (Postfix) with ESMTP id E5C8111F60AF for ; Wed, 26 Apr 2006 08:49:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 9E2492B5A0; Wed, 26 Apr 2006 14:49:19 +0300 (EEST) Received: from ar-sd.net ([127.0.0.1]) by localhost (ar-sd.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15698-06; Wed, 26 Apr 2006 14:49:16 +0300 (EEST) Received: from forge (unknown [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id AD3382B59E; Wed, 26 Apr 2006 14:49:16 +0300 (EEST) Message-ID: <02b801c66927$78642d70$0b00a8c0@mpsro.dom> From: "Andy" To: "Andy" , References: <027501c66866$ff0999d0$0b00a8c0@mpsro.dom> Subject: Re: Database LATIN1 to UFT-8 (unicode) converting problem SOLVED Date: Wed, 26 Apr 2006 14:49:26 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02B5_01C66940.9D357EB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/276 X-Sequence-Number: 21445 This is a multi-part message in MIME format. ------=_NextPart_000_02B5_01C66940.9D357EB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I found a solution: I re-run initdb with Unicode encoding and now seems = to work fine.=20 I cannot figure out why did this happen, or does the initdb encoding = affects all the databases or the db encoding is not enough to be = specified? Andy. ----- Original Message -----=20 From: Andy=20 To: pgsql-admin@postgresql.org=20 Sent: Tuesday, April 25, 2006 3:51 PM Subject: [ADMIN] Database LATIN1 to UFT-8 (unicode) converting problem Hi to all,=20 We just tried to switch out database from LATIN 1 (ISO 8859-1) to = UTF-8. After a few tests we found out some problems: - the upper and lower functions does not work for all characters. = Especially lower returns nothing if a umlaut is in the converted string. = The umlauts are not converted at all. - the returned rows are not correctly sorted. =F6 is before a and so = on.=20 The server is a Suse 10 system. DB is Postgresql 8.0.3.=20 This sorting problem we had it before and it was the problem was at = local system settings. Now everything is switched to UTF-8 (or it seems = so).=20 Please advise.=20 Thank you, Andy. ------=_NextPart_000_02B5_01C66940.9D357EB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I found a solution: I re-run initdb with Unicode encoding and now seems to work = fine.=20
 
I cannot figure out why did this = happen, or does=20 the initdb encoding affects all the databases or the db encoding is not = enough=20 to be specified?
 
Andy.
 
----- Original Message -----
From:=20 Andy =
Sent: Tuesday, April 25, 2006 = 3:51=20 PM
Subject: [ADMIN] Database = LATIN1 to UFT-8=20 (unicode) converting problem

Hi to all,
 
We just tried to switch out database = from LATIN 1=20 (ISO 8859-1) to UTF-8. After a few tests we found out some=20 problems:
 - the upper and lower functions = does not=20 work for all characters. Especially lower returns nothing if a umlaut = is in=20 the converted string. The umlauts are not converted at = all.
- the returned rows are not correctly = sorted. =F6=20 is before a and so on.
 
The server is a Suse 10 system. DB is = Postgresql=20 8.0.3.
 
This sorting problem we had it before = and it was=20 the problem was at local system settings. Now everything is switched = to UTF-8=20 (or it seems so).
 
Please advise.
 
Thank you,
Andy.
 
------=_NextPart_000_02B5_01C66940.9D357EB0--