ODBC driver problem ??

From: Pierre-Louis Malatray <pierrelouis(dot)malatray(at)free(dot)fr>
To: pgsql-hackers(at)postgresql(dot)org
Subject: ODBC driver problem ??
Date: 2000-06-16 21:40:02
Message-ID: 394A9EB1.28B97069@free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi everybody,

I would like first to thank you all for the very good job done in
PostGreSQL.

You say that you don't look for performance, but I can tell that
Postgres on Linux
is as fast as Sybase on windows.

I use Postgres for a couple of years now, with windows clients and I
recently use the text type.
It is when I discovered a problem :

When I record a field containing CRLF (update or insert), one leading
caracter is rubbed off
for each CRLF encountered, when I see it back in the windows
application.

For example : I record "Hello\r\nworld" and I see back "ello\r\nworld"

psql shows "Hello\nworld"

The field is recorded correctly when watching it with psql, that is to
say with all caracters in
but with LF instead of CRLF.

The external way I found to get around the problem is to add a leading
space for each CRLF
encountered in the string when recording it in the database, so that all
seems to be correct
from the client.

So I think that the problem is coming from the ODBC driver that try to
transform LF in CRLF.

I hope that all this is clear :-)

I currently use postgresql-6.4.2 on a RedHat 6.0.
The ODBC driver version is 6.40.0002 configured with 6.4 protocol, all
defaults except the ReadOnly option
which is off.

I hope not to have bored you with all this :-))

You may have questions but I am *NOT* on the mailing list...

Thank you

Pierre-Louis

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2000-06-16 22:28:20 Re: Changes to functions and triggers
Previous Message Ross J. Reedstrom 2000-06-16 21:07:13 Re: Big 7.1 open items