Re: make == as = ?

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: make == as = ?
Date: 2004-04-08 16:26:03
Message-ID: Pine.LNX.4.33.0404081024040.10659-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 8 Apr 2004, Bruce Momjian wrote:

> Fabien COELHO wrote:
> >
> > > > This would help me, at least, write correct and portable SQL. :)
> > >
> > > Added to TODO:
> > >
> > > * Add a session mode to warn about non-standard SQL usage
> >
> > So it seems that having C-like operators would hurt a lot;-)
> >
> > So you want to generate warnings for SERIAL, TEXT and a bunch of other
> > types, WITH[OUT] OIDS, RULE, ~ regular expressions, arrays, any use of
> > pg_catalog instead of information_schema (I may be wrong in the list, I
> > don't have the standard at hand, but I think I'm right in the spirit)...
> >
> > This is going to be noisy;-)
>
> Yep, it sure is going to be noisy.

Could we consider a three (or more) way setting, for what to do?
Something like:

sql_noncompliance_mode = error;
sql_noncompliance_mode = warn / notice;
sql_noncompliance_mode = ignore;

Just wondering...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2004-04-08 16:31:22 Re: PostgreSQL configuration
Previous Message Tom Lane 2004-04-08 15:47:25 Re: locale