Re: Parsing of backslash in statements via ODBC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "aboster" <aboster(at)at-sd(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Parsing of backslash in statements via ODBC
Date: 2005-01-14 21:43:14
Message-ID: 26406.1105738994@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"aboster" <aboster(at)at-sd(dot)com> writes:
> Since MS-SQL & Oracle (both via ODBC) work fine with this app, I would
> suspect the issue is that Postgres is interpreting backslashes as escape
> characters in situations that the supported databases do not.

Postgres definitely considers backslashes to be escape characters in
string literals.

> Has anyone run across something like this, and if so, can anything be done
> given that we don't have the source code of the application in question?

Without the app source code you may be kinda stuck :-(. It's possible
that you could hack something at the ODBC level, though. Try asking on
the pgsql-odbc list.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-01-14 21:55:47 Re: MOVE
Previous Message J. Greenlees 2005-01-14 21:39:56 Re: ntfs for windows port rc5-2