Re: escape string type for upcoming 8.1 - Mailing list pgsql-general

From Greg Stark
Subject Re: escape string type for upcoming 8.1
Date
Msg-id 87wtmta5bg.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: escape string type for upcoming 8.1  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: escape string type for upcoming 8.1  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: escape string type for upcoming 8.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Bruce Momjian <pgman@candle.pha.pa.us> writes:

> > What happens if someone already has a type called "e" ?
>
> That would be the same problem as someone having a type 'b' or 'x'.  It
> would still work, but not for casts like text'str'.  Those letters are
> caught in the lexer before getting into to the parser.

What I'm asking about is, are there going to be user applications that were
working fine in previous versions but suddenly start breaking when this change
is made? Does that affect your decision in whether to backport this to 8.0.x?

--
greg

pgsql-general by date:

Previous
From: Shane
Date:
Subject: Re: Index not being used unless enable_seqscan=false
Next
From: Michael Fuhr
Date:
Subject: Re: function accepting a row