Re: Parsing of backslash in statements via ODBC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Given that this issue is a violation of SQL compatibility, shouldn't
there really be an option to turn off interpretation of backslash
characters in string literals as escapes?  Maybe as a session variable
of some kind, with a default being set in postgresql.conf?

On Jan 14, 2005, at 4:43 PM, Tom Lane wrote:

> "aboster" <aboster@at-sd.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
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
>                http://archives.postgresql.org
>
>
- -----------------------------------------------------------
Frank D. Engel, Jr.  <fde101@fjrhome.net>

$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten
Son, that whosoever believeth in him should not perish, but have
everlasting life.
$
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFB6EDd7aqtWrR9cZoRAguTAJ9sij6xZ2Xmd2XfcEzeE1Wu4tVfuwCfcj6B
MIPrLSXexDnl36k7ubDIEUg=
=7H3R
-----END PGP SIGNATURE-----



___________________________________________________________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com