X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 96B679FA65C for ; Tue, 25 Jul 2006 14:39:55 -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 71162-10 for ; Tue, 25 Jul 2006 14:39:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail11.bluewin.ch (mail11.bluewin.ch [195.186.18.61]) by postgresql.org (Postfix) with ESMTP id 37AF89FA491 for ; Tue, 25 Jul 2006 14:39:50 -0300 (ADT) Received: from [192.168.1.74] (83.78.158.96) by mail11.bluewin.ch (Bluewin 7.3.110.2) id 44A3D2BF005E7D69 for pgsql-admin@postgresql.org; Tue, 25 Jul 2006 17:39:48 +0000 From: Ivo Rossacher To: pgsql-admin@postgresql.org Subject: Re: UTF8 characters Date: Tue, 25 Jul 2006 19:39:32 +0200 User-Agent: KMail/1.8.2 References: <20060714154218.10234.qmail@web55703.mail.re3.yahoo.com> <200607211842.14935.peter_e@gmx.net> <1c66bda80607250327k445186cesa5e36430929a4a22@mail.gmail.com> In-Reply-To: <1c66bda80607250327k445186cesa5e36430929a4a22@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607251939.33084.rossacher@bluewin.ch> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200607/209 X-Sequence-Number: 22455 Well the server does have the capability to convert from the server encoding to the client encoding and the other way around. To get this working you need a server encoding which can be convertet to the clientencoding. UNICODE (UTF8) is a good starting point here. Now the server needs to know waht the encoding of the client is. You can set the client encoding from the client by sending "set client_encoding to " to the server after the connection is started. There are other ways which can solve other problems (see character set support in the manual), for my application this way wroked best and makes it simple to work with different clientencodings. Best regards Ivo Am Dienstag, 25. Juli 2006 12.27 schrieb adey: > I had the same problem when upgrading v7.4 database to v8, SQL-ASCII to > UTF8 - we had to replace single backslashes with double backslashes in the > v7 database to get the data to display correctly, then dump and restore in > v8 / UTF8. Have we done something wrong please? > > On 7/22/06, Peter Eisentraut wrote: > > PostgreSQL Admin wrote: > > > I had my database set to SQL_ASCII and switched to UTF8, but now I > > > notice that I must add a slash for periods/dots ( \. vs . ) to insert > > > into varchar. Is this normal? > > > > No. > > > > -- > > Peter Eisentraut > > http://developer.postgresql.org/~petere/ > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 4: Have you searched our list archives? > > > > http://archives.postgresql.org