Re: Escape handling in strings

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

Tom Lane wrote:
> 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.

Right, the GUC read-only variables are already in the patch URL I
posted.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2005-06-21 17:03:06 Re: Scripting issues
Previous Message Tom Lane 2005-06-21 15:38:36 Re: index selection by query planner

Browse pgsql-hackers by date

  From Date Subject
Next Message Victor Y. Yegorov 2005-06-21 16:45:57 Re: Schedule for 8.1 feature freeze
Previous Message Andrew Dunstan 2005-06-21 16:06:37 Re: Schedule for 8.1 feature freeze