X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 34F94D1EF18 for ; Mon, 3 May 2004 17:51:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 37528-10 for ; Mon, 3 May 2004 17:51:01 -0300 (ADT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 6720DD1EDE5 for ; Mon, 3 May 2004 17:50:55 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id C6D8D55EF0; Mon, 3 May 2004 22:51:02 +0200 (CEST) Received: from colt.pezone.net (dsl-082-082-239-156.arcor-ip.net [82.82.239.156]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 5C54455EEC; Mon, 3 May 2004 22:51:02 +0200 (CEST) From: Peter Eisentraut To: Martin Zdila , pgsql-admin@postgresql.org Subject: Re: windows-1250 encoding Date: Mon, 3 May 2004 22:51:01 +0200 User-Agent: KMail/1.5.1 References: <409636A1.2020609@antik.sk> In-Reply-To: <409636A1.2020609@antik.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200405032251.01714.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/23 X-Sequence-Number: 13339 Martin Zdila wrote: > How can one set character encoding in the database to windows-1250? Evidently you cannot. > I just need to order selected rows by some column witch windows-1250 > encoded text. If you have windows-1250 data on the client side, then declare your client encoding, create your database with a supported encoding, and the conversion will be done for you. If you really have windows-1250 data already in your database, then, uh, how did you do that, considering that that encoding is not supported for databases?