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

Re: non-standard escapes in string literals

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: F Harvell <fharvell(at)fts(dot)net>,Andrew Pimlott <pimlott(at)idiomtech(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: non-standard escapes in string literals
Date: 2002-04-25 20:22:10
Message-ID: 200204252022.g3PKMA814482@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> F Harvell <fharvell(at)fts(dot)net> writes:
> > This also poses the biggest problem in terms of legacy compatibility.
> > Perhaps the answer is to add a runtime config option (and default it
> > to ANSI) and possibly deprecate the C escaping.
> 
> While I wouldn't necessarily object to a runtime option, I do object
> to both the other parts of your proposal ;-).  Backslash escaping is
> not broken; we aren't going to remove it or deprecate it, and I would
> vote against making it non-default.

Added to TODO:

 * Allow backslash handling in quoted strings to be disabled for portability

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2002-04-25 20:26:26
Subject: Re: md5 passwords and pg_shadow
Previous:From: Michael LoftisDate: 2002-04-25 20:19:33
Subject: Re: What is wrong with hashed index usage?

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