Re: SQL:2011 features - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SQL:2011 features
Date
Msg-id 1325530060.15294.4.camel@vanquo.pezone.net
Whole thread Raw
In response to SQL:2011 features  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: SQL:2011 features  (Simon Riggs <simon@2ndQuadrant.com>)
Re: SQL:2011 features  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: SQL:2011 features  ("David E. Wheeler" <david@justatheory.com>)
List pgsql-hackers
On mån, 2012-01-02 at 09:33 +0000, Simon Riggs wrote:
> Are there any features in SQL:2011 that we should be considering for 9.2?
> 
> We seem quite close on temporal stuff, so maybe just a little syntax work?

I am aware of this piece on what's new in SQL:2011:
http://petereisentraut.blogspot.com/2010/04/news-from-sql-standard.html

Based on that:

* ALTER TABLE ... ALTER COLUMN ... SET/DROP NOT NULL: done since PG 7.3

* Constraints set to NO ENFORCE: Apparently no current interest; more
interest in the NOT VALID track at the moment.

* System-versioned tables: Hmm, just a little syntax work? Not sure how
much interest there is.

* Combined data change and retrieval: We decided against supporting the
standard syntax for this.

* Named arguments in function calls: done since PG 9.0; and we're
phasing out the => operator.

* Default values for function arguments: done since PG 9.0




pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe
Next
From: Simon Riggs
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe