Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 732129FBC40 for ; Thu, 22 Mar 2007 16:01:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 70257-02-3 for ; Thu, 22 Mar 2007 16:00:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail15.bluewin.ch (mail15.bluewin.ch [195.186.18.63]) by postgresql.org (Postfix) with ESMTP id 8F1809FA32B for ; Thu, 22 Mar 2007 16:01:01 -0300 (ADT) Received: from [192.168.1.74] (83.79.100.240) by mail15.bluewin.ch (Bluewin 7.3.121) id 45F50C83003443CF for pgsql-admin@postgresql.org; Thu, 22 Mar 2007 19:01:00 +0000 From: Ivo Rossacher To: pgsql-admin@postgresql.org Subject: Re: Encoding problems Date: Thu, 22 Mar 2007 20:00:59 +0100 User-Agent: KMail/1.9.5 References: <938bcd6f0703220607g1d099e45mb266f8cc4f085de5@mail.gmail.com> In-Reply-To: <938bcd6f0703220607g1d099e45mb266f8cc4f085de5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200703222000.59688.rossacher@bluewin.ch> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/164 X-Sequence-Number: 24988 show client_encoding displays the encoding to which the server currently i= s=20 converting. With set client_encoding to UNICODE; you can change the=20 client_encoding on the fly and check if the results becomes better. I am no= t=20 sure how to adjust the client_encoding in pgAdmin so that this will be set = at=20 startup automtically. There is a default client_encoding stored in the serv= er=20 as well but there you have to check if it interfers with your other=20 interfaces. Best regards Ivo Am Donnerstag, 22. M=E4rz 2007 14:07 schrieb Bjarni Ragnarsson: > Hi everyone. > > I have some encoding problems like many others. > > I'm using Python (and Django) with my PostgreSQL 8.2 and pgAdmin > 1.6.2 on Windows XP Pro. The default encoding here in Iceland is > win1252. I have a database with that encoding. > > The problem is that pgAdmin seems to use utf8 no matter what I do. > The data seems to be stored correctly when entered via a web-page, but > when displayed via pgAdmin it's corrupted (that is the special > characters don't show correctly). pgAdmin seems to presume the data > is in utf8 format despite the database settings. Entering data via > pgAdmin results in corrupted data on the web likewise. > > Is this a bug or is there some setting I've overlooked? > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match