X-Original-To: pgsql-bugs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C57763A29A7 for ; Sat, 15 Jan 2005 04:13:31 +0000 (GMT) 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 69091-08 for ; Sat, 15 Jan 2005 04:13:29 +0000 (GMT) Received: from sunsite.dcc.uchile.cl (sunsite.dcc.uchile.cl [192.80.24.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7E03E3A299E for ; Sat, 15 Jan 2005 04:13:28 +0000 (GMT) Received: from anakena.dcc.uchile.cl ([192.80.24.3]) by sunsite.dcc.uchile.cl (8.12.11/8.12.11) with ESMTP id j0F4DH8Z018378; Sat, 15 Jan 2005 01:13:17 -0300 (CLST) Received: by anakena.dcc.uchile.cl (Postfix, from userid 4151) id 37D7452E50; Sat, 15 Jan 2005 01:13:17 -0300 (CLST) Date: Sat, 15 Jan 2005 01:13:17 -0300 From: Alvaro Herrera To: "Elvis E. Henriquez A." Cc: pgsql-bugs@postgresql.org Subject: Re: Bug Report Message-ID: <20050115041317.GA5541@dcc.uchile.cl> References: <000101c4f7d4$2b9c2f80$0c74c4a1@henriquez> <20050114140314.GC21340@dcc.uchile.cl> <001601c4faa4$d8a32e90$ec75c4a1@henriquez> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050114140314.GC21340@dcc.uchile.cl> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.343 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200501/166 X-Sequence-Number: 10599 On Fri, Jan 14, 2005 at 09:50:32PM -0400, Elvis E. Henriquez A. wrote: Hi, Please keep the copy to the list when replying. > C:\Documents and Settings\Elvis>psql -h localhost -U postgres -f Update13.sql prueba > could not find a "psql" to execute > Password: > could not find a "psql" to execute Now that's weird. But I don't think it's a Postgres problem; maybe your shell is playing some games on you. I don't know a lot about Hasefroch command line utilities to help you more here. > About the ODBC problem, I don't think it's an encoding problem. > My database encoding is sql_ascii, which I'm being using since > postgresql 7.3.2, and worked perfectly. If I use, for example, pgAdmin > III or phpPgAdmin, data is perfectly displayed. But when I make a > select statement through the ODBC driver, using for example Visual > Basic 6 with ADO, the data seems to be damaged, I think that's exactly the problem. With SQL_ASCII you should limit yourself to (7 bit) ASCII characters, or be bitten by Postgres' recoding capabilities. If you want to use non-ascii characters, you should declare your database as LATIN1 or LATIN9, or if it's a Hasefroch server maybe win125x, cp850, whatever. And your client_encoding should be set to the correct value, so that if there is gonna be character conversion, the results are what you expect. -- Alvaro Herrera () "La primera ley de las demostraciones en vivo es: no trate de usar el sistema. Escriba un guión que no toque nada para no causar daños." (Jakob Nielsen)