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

From Fabien COELHO
Subject Re: make == as = ?
Date
Msg-id Pine.LNX.4.58.0404101104270.2356@honfleur
Whole thread Raw
In response to Re: make == as = ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: make == as = ?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
> > 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.

Hmmm.

I could think of:
sql_version = sql2/sql92/sql3/sql99/postgresql/oracle/mysql/extended

Or maybe with a simple integer...
sql_strict_compliance = on/off

On strict, errors could be generated for incompatible features in user
sql queries. Otherwise, only warnings or notice appear for misfeatures.

It would be possible to mimic (theoretically) other SQL implementations.

With "extended", I could have c-like operators;-) : ! && || == !=

Still dreaming.

-- 
Fabien Coelho - coelho@cri.ensmp.fr


pgsql-hackers by date:

Previous
From: rm_pg@cheapcomplexdevices.com
Date:
Subject: Re: PostgreSQL configuration
Next
From: Fabien COELHO
Date:
Subject: Re: make == as = ?