pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@dcc.uchile.cl>
To: Elvis E. Henriquez A. <elvish@cantv.net>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Bug Report
Date: Sat, 15 Jan 2005 01:13:17 -0300
Message-ID: <20050115041317.GA5541@dcc.uchile.cl> (raw)
In-Reply-To: <20050114140314.GC21340@dcc.uchile.cl>
References: <000101c4f7d4$2b9c2f80$0c74c4a1@henriquez>
	<20050114140314.GC21340@dcc.uchile.cl>
	<001601c4faa4$d8a32e90$ec75c4a1@henriquez>

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 (<alvherre[@]dcc.uchile.cl>)
"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)



view thread (28+ messages)  latest in thread

Message-ID: <20050115041317.GA5541@dcc.uchile.cl>
Permalink:  ../20050115041317.GA5541@dcc.uchile.cl/
Also on:    postgresql.org/message-id/20050115041317.GA5541@dcc.uchile.cl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: alvherre@dcc.uchile.cl, elvish@cantv.net
  Subject: Re: Bug Report
  In-Reply-To: <20050115041317.GA5541@dcc.uchile.cl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox