Re: [GENERAL] Removing pollution from log files

> Apart from that: there was a bug in the ODBC driver prior 08.02.0402 which > resulted in this error message whenever binary data of type > SQL_LONGVARBINARY > was send. Where is 0402 driver ? Last downloadable version in 0400 which has this issue. Andrus. ---(end o

Re: [GENERAL] Removing pollution from log files

Andrus wrote: >> Apart from that: there was a bug in the ODBC driver prior 08.02.0402 which >> resulted in this error message whenever binary data of type >> SQL_LONGVARBINARY >> was send. > >Where is 0402 driver ? The snapshot drivers can be found here:

Re: [GENERAL] Removing pollution from log files

Andrus wrote: > > That's not pollution; it's telling you you need to fix your > > application to escape the backslashes differently. > > I havent seen that ODBC specification requires escaping strings. > So this is task of ODBC driver. So complain to the ODBC guys. OTOH, maybe you are using ODBC

Re: [GENERAL] Removing pollution from log files

> That's not pollution; it's telling you you need to fix your > application to escape the backslashes differently. I havent seen that ODBC specification requires escaping strings. So this is task of ODBC driver. Andrus. ---(end of broadcast)---

Re: [GENERAL] Removing pollution from log files

Andrew Sullivan wrote: >On Mon, Aug 27, 2007 at 02:00:02PM +0300, Andrus wrote: >> Postgres log files are polluted with messages >> >> 2007-08-27 06:10:38 WARNING: nonstandard use of \\ in a string literal at >> character 190 >> 2007-08-27 06:10:38 HINT: Use the escape string syntax for backsl

Re: [GENERAL] Removing pollution from log files

On Mon, Aug 27, 2007 at 02:00:02PM +0300, Andrus wrote: > Postgres log files are polluted with messages > > 2007-08-27 06:10:38 WARNING: nonstandard use of \\ in a string literal at > character 190 > 2007-08-27 06:10:38 HINT: Use the escape string syntax for backslashes, > e.g., E'\\'. That's