Search Postgresql Archives

Re: Parsing of backslash in statements via ODBC

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

 



"aboster" <aboster@xxxxxxxxx> 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

[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