Re: escape_string_syntax

Nicolas Neuss <[email protected]> writes:

> Nicolas Neuss <[email protected]> writes:
>
>> I have a problem/question which might be already resolved in recent
>> versions of CLSQL.  I use CLSQL 4.0.3.1 together with Postgresql 8.3,
>> and observe that it emits the following messages (when putting
>> LaTeX-code in my database):
>>
>> WARNING:  nonstandard use of \\ in a string literal
>> LINE 1: ...ITLE = 'Oktalsystem in Dezimalsystem 1',CONTENT = 'Sei $1023...
>>                                                              ^
>> HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
>>
>> I have seen that I can disable this warning by setting 
>>   escape_string_warning = off
>> in "postgresql.conf".  However, this would not be optimal, because later
>> Postgresql versions might require the escaped syntax.  
>
> For the record: Instead of suppressing the warning, I have put now
>   standard_conforming_strings = on
> in 'postgresql.conf'.
>
> (See 
> http://www.network-theory.co.uk/docs/postgresql/vol3/PreviousPostgreSQLVersions.html#SEC63).

This does not work (I should have tested it more before posting to the
list again).  When I switch on standard_conforming_strings I can not any
more enter single backslashes into my database via CLSQL.  Therefore, I
think that CLSQL's postgresql interface (at least for the 4.0.3.1
version from Debian which I am using) expects Postgresql as treating
backslash as an escape character.  Unfortunately, I could not find
where.

Hmm, so for the moment I have gone back to:

  standard_conforming_strings = off
  escape_string_warning = off

Nicolas