From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | "Frank D(dot) Engel, Jr(dot)" <fde101(at)fjrhome(dot)net> |
Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Parsing of backslash in statements via ODBC |
Date: | 2005-01-14 22:19:33 |
Message-ID: | 20050114221932.GF1724@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jan 14, 2005 at 04:59:57PM -0500, Frank D. Engel, Jr. wrote:
> 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?
I'm not totally sure about how ODBC works, but if it's anything like
Perl DBI, surely it's the responsibility of the ODBC layer to escape
the baackslashes? Maybe it depends on whether they're using
placeholders or not...
Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | J. Greenlees | 2005-01-14 22:40:53 | Re: ntfs for windows port rc5-2 |
Previous Message | Jaime Casanova | 2005-01-14 22:16:16 | developers map |