Re: Feature Request: DDL + RegExp - definitions - Mailing list pgsql-general

From Tom Lane
Subject Re: Feature Request: DDL + RegExp - definitions
Date
Msg-id 16386.1314209966@sss.pgh.pa.us
Whole thread Raw
In response to Re: Feature Request: DDL + RegExp - definitions  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-general
Merlin Moncure <mmoncure@gmail.com> writes:
> On Wed, Aug 24, 2011 at 11:30 AM, Richard Broersma
>> The following email illustrates the behavior that is undesirable (to me).
>> http://www.mail-archive.com/pgadmin-support@postgresql.org/msg11482.html

> this is IMO not a feature, but a bug.

No, it's not a bug, it's just an unfortunate side-effect of the pushups
we've had to go through to get to standard conforming strings.

I seriously doubt that we would add a feature of the sort Richard
suggests, because with standard_conforming_strings turned on (which is
the default as of 9.1), there is no issue.  Forcing E'' syntax would
make the results of pg_getviewdef less standards-compliant, not more so,
and that's not a direction we want to go in.

If you find the warnings about backslashes annoying and unhelpful, you
can turn off escape_string_warning --- they're only there to help
identify code that is likely to have an issue when moved to an
environment with standard_conforming_strings turned on.

            regards, tom lane

pgsql-general by date:

Previous
From: ivan_14_32
Date:
Subject: Re: "OLD." || myColumnNameVar (How to generically access columns in a trigger's OLD or NEW records)
Next
From: Tom Lane
Date:
Subject: Re: plperlu function caused a segmentation fault