Re: Escape handling in strings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Escape handling in strings
Date: 2005-06-21 13:11:07
Message-ID: 1741.1119359467@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Bruce Momjian wrote:
>> I have received very few replies to my suggestion that we implement E''
>> for escaped strings, so eventually, after a few major releases, we can
>> have '' treat backslashes literally like the SQL standard requires.

> Just checking: with this plan, a client needs to know what server
> version is in use to correctly escape strings, correct? That is, there
> is no escape mechanism that works correctly for both "old" and "new"
> servers?

When the change happens, yes, it will be non compatible. I don't
recommend thinking of it as a "server version" check though --- we
will put in a read-only GUC variable (like the one for integer
datetimes) and you can check it through the parameter reporting
mechanism.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2005-06-21 13:20:43 Re: compilation postgresql/solaris error
Previous Message Jason Tesser 2005-06-21 12:56:19 Re: problems with types after update to 8.0

Browse pgsql-hackers by date

  From Date Subject
Next Message Mag Gam 2005-06-21 13:16:34 Re: Compiling tsearch2 on AIX
Previous Message Eugen Nedelcu 2005-06-21 13:03:43 Re: thousands comma numeric formatting in psql