Date: Wed, 13 Oct 2004 17:29:02 -0700
From: elein <elein@varlena.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: SQL 2003 conformance
Message-ID: <20041013172902.H14574@cookie.varlena.com>
Mail-Followup-To: Peter Eisentraut <peter_e@gmx.net>,
 pgsql-docs@postgresql.org
References: <200410121952.24859.peter_e@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410121952.24859.peter_e@gmx.net>
User-Agent: Mutt/1.3.22.1i

I have a couple of the new features written up, but nothing
like an entire review.  If someone can tackle this job
and wants help, I'll help (but I cannot sign up for the
whole thing).  Or if someone wants the material
on the items I have done, just email me.

--elein
elein@varlena.com

On Tue, Oct 12, 2004 at 07:52:24PM +0200, Peter Eisentraut wrote:
> Is anyone feeling masochistic and wants to review the SQL standards 
> conformance chapter in the documentation for SQL 2003?  I know that 
> several features were added or revised for SQL 2003 conformance, so it 
> would be nice to have that documented for the 8.0 release.
> 
> I think an overview of how the structure of SQL 2003 differs from SQL 
> 1999 would also help the group to analyse the individual feature groups 
> more quickly.
> 
> -- 
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match