Re: #escape_string_warning = off

From: Jeff Davis <jdavis-pgsql(at)empires(dot)org>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: #escape_string_warning = off
Date: 2005-08-02 06:05:13
Message-ID: 42EF0D19.7070004@empires.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The documentation about this is a little brief (reading from the
developer docs, section 4.1.2.1.).

Does the SQL standard provide no way to have a NULL character in a
string constant? Is single-quote the only special character?

If I have a system on 7.4 or 8.0 right now, what is the recommended
"right" way to write string constants with backslashes? I can't use E''
yet, so if I need to include a backslash it seems like there's no chance
it will be forward-compatible.

In the E'' constants, the special characters are only single-quote,
backslash, and NULL right?

Regards,
Jeff Davis

Marko Kreen wrote:
> On Mon, Aug 01, 2005 at 11:58:34AM -0700, Joshua D. Drake wrote:
>
>>What might this be?
>
>
> Whether to warn on '\' in non-E'' strings.
>
> AFAIK Bruce wants to turn this to 'on' in 8.2.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2005-08-02 07:25:00 Re: Autovacuum to-do list
Previous Message mark 2005-08-02 04:55:28 Re: Autovacuum to-do list