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

From Bruce Momjian
Subject Re: make == as = ?
Date
Msg-id 200404081639.i38GdoE23074@candle.pha.pa.us
Whole thread Raw
In response to Re: make == as = ?  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: make == as = ?  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
scott.marlowe wrote:
> 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;

I think a boolean that turns on warnings would be enough.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: make == as = ?
Next
From: Tom Lane
Date:
Subject: Re: Function to kill backend