Re: Possible to run the server with ANSI/ISO string escapeing - Mailing list pgsql-general

From Ken Johanson
Subject Re: Possible to run the server with ANSI/ISO string escapeing
Date
Msg-id 421F45AF.5010800@kensystem.com
Whole thread Raw
In response to Re: Possible to run the server with ANSI/ISO string escapeing  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Possible to run the server with ANSI/ISO string escapeing  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Bruce Momjian wrote: <blockquote cite="mid200502250053.j1P0rDm09001@candle.pha.pa.us" type="cite"><pre wrap="">Ken
Johansonwrote: </pre><blockquote type="cite"><pre wrap="">Greetings,
 

Does anyone know if it will be possible to run the server with ANSI/ISO 
string escaping instead of C-style escapes? The C style escaping is a 
shoot-down for our adoption of postgres, since its non-standard.   </pre></blockquote><pre wrap="">
Not yet, but we have a TODO item:
* Allow backslash handling in quoted strings to be disabled for  portability  The use of C-style backslashes (.e.g. \n,
\r)in quoted strings is not  SQL-spec compliant, so allow such handling to be disabled.
 

Uh, what is ANSI/ISO escaping actually?  I assume you mean only
supporting '' for literal quotes rather than \' too.
 </pre></blockquote> Yes Sir. Being able to disable the backslash-escaping is the desired operation. In circles of
businessdeciding wether to move to opensource databases this is the silently used excuse (by the critics) to dismiss pg
sinceits arguably so fundamental and somewhat dangerous (data loss). Getting pg to behave 'normally' would silence this
excuse.<br/><br /> Is there anything I can do to help move this up the todo list?<br /><br /> Thanks,<br /> ken<br /> 

pgsql-general by date:

Previous
From: Richard_D_Levine@raytheon.com
Date:
Subject: Re: postgresql 8.0 advantages
Next
From: Dave Smith
Date:
Subject: JDBC and Portals . Clarification