Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Escape handling in strings

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <andrew(at)dunslane(dot)net>, <pg(at)rbt(dot)ca>,<pgsql-hackers(at)postgresql(dot)org>, <chriskl(at)familyhealth(dot)com(dot)au>
Subject: Re: [PATCHES] Escape handling in strings
Date: 2005-06-17 01:03:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian said:

> OK, the current patch warns about two things, \' with one message, and
> any backslash in a non-E string with a different message.  The \'
> message can easily be avoided in clients even in 8.0 by using '', but
> for E'', there is no way to prepare an application before upgrading to
> 8.1 because 8.0 doesn't have E''.  (We can add E'' in a subrelease, but
> what percentage of users are going to upgrade to that?)  This is why I
> think we need to add a GUC to allow the warning to be turned off.  To
> be clear, the GUC is to control the warning, not the query behavior.
> We could go with the second warning only in 8.2, but that seems too
> confusing --- we should deal with the escape issue in two stages,
> rather than three.

So you don't agree with Tom's suggestion to implement E'' a full cycle
before removing backslash processing in standard strings? Or have I
misunderstood again?



In response to


pgsql-hackers by date

Next:From: Tim AllenDate: 2005-06-17 01:04:33
Subject: Re: Autovacuum in the backend
Previous:From: Josh BerkusDate: 2005-06-17 00:31:37
Subject: DTrace Probes?

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-06-17 01:41:05
Subject: Re: [PATCHES] Escape handling in strings
Previous:From: Bruce MomjianDate: 2005-06-16 17:53:59
Subject: Re: fsync under win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group