X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 89BAB52ADC for ; Tue, 9 Aug 2005 12:59:58 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88859-08 for ; Tue, 9 Aug 2005 15:59:50 +0000 (GMT) Received: from svana.org (svana.org [203.20.62.76]) by svr1.postgresql.org (Postfix) with ESMTP id 3E68D52AA2 for ; Tue, 9 Aug 2005 12:59:49 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 3.35 #1 (Debian)) id 1E2WW2-00043o-00; Wed, 10 Aug 2005 01:59:46 +1000 Date: Tue, 9 Aug 2005 17:59:46 +0200 From: Martijn van Oosterhout To: Salem Berhanu Cc: pgsql-general@postgresql.org Subject: Re: postgres & server encodings Message-ID: <20050809155946.GF8244@svana.org> Reply-To: Martijn van Oosterhout Mail-Followup-To: Salem Berhanu , pgsql-general@postgresql.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9crTWz/Z+Zyzu20v" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: X-Warning: Normally my messages are signed, but not on the ozTiVo list due to legacy application support X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200508/452 X-Sequence-Number: 81860 --9crTWz/Z+Zyzu20v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 08, 2005 at 04:10:50PM +0000, Salem Berhanu wrote: > What exactly is the SQL_ASCII encoding in postgres? I have a pg=20 > installation with an SQL_ASCII server encoding and my database (also=20 > SQL_ASCII) seems to be able to handle all types of encodings? how is this= =20 > possible? is this what the server & db encoding needs to be set to in ord= er=20 > to handle various encodings? SQL_ASCII means that the database does no locale specific or language specific encoding ever. It won't check what you send it either. If you're content to let clients deal with any encoding issues, this may be what you want. But anything to do with lower(), upper(), case-insenstive in the database itself will be totally stupid since it's assuming ASCII. > Also is there a way of dumping data from an SQL_ASCII db to a UNICODE db.= =20 > Creating a dump and converting with a tool like iconv is probably not an= =20 > option since the data in the SQL_ASCII db has unknown/inconsistant encodi= ng. > Please let me know as soon as possible. This is a messy situation. Since the system can't guess your encoding you'd have to fix it all up yourself... Hope this helps, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. --9crTWz/Z+Zyzu20v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFC+NLxIB7bNG8LQkwRAvwBAJ9TEqg+F4KzGEB6IPXMnzK0k9XdVQCdETqE IBaaC/nniJJizq7iz3o0zvU= =mFIG -----END PGP SIGNATURE----- --9crTWz/Z+Zyzu20v--