Re: make == as = ? - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: make == as = ?
Date
Msg-id Pine.LNX.4.33.0404081024040.10659-100000@css120.ihs.com
Whole thread Raw
In response to Re: make == as = ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: make == as = ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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...



pgsql-hackers by date:

Previous
From: pgsql@mohawksoft.com
Date:
Subject: Re: PostgreSQL configuration
Next
From: Bruce Momjian
Date:
Subject: Re: make == as = ?