Search Postgresql Archives

Re: Parsing of backslash in statements via ODBC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>   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.

Attachment: pgpNRD1lXichR.pgp
Description: PGP signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux