[PostgreSQL-Hackers] SQL:2011 features

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

I saw this as well, which seems quite different:

http://metadata-standards.org/Document-library/Documents-by-number/WG2-N1501-N1550/WG2_N1536_koa046-Temporal-features-in-SQL-standard.pdf

Hello

2012/1/2 Peter Eisentraut <peter_e@gmx.net>:
trim_array can be simply implemented for one dim array. I am not sure
about semantic for multidim arrays.

Regards

Pavel

We don’t support `=>` for params yet, right? Still just `:=`?

David

I assume you guys know where to go to get the complete sql:2011 spec:

http://www.iso.org/iso/search.htm?qt=9075&searchSubmit=Search&sort=rel&type=simple&published=true

But if time/money is an issue the following seems to be the best publicly
available description of the temporal features:

http://metadata-standards.org/Document-library/Documents-by-number/WG2-N1501-N1550/WG2_N1536_koa046-Temporal-features-in-SQL-standard.pdf

If/as you all make progress with this we would love to hear about it in the
"Temporal Data" group on LinkedIn, where we are discussing temporal data in
general and the SQL:2011 extensions in particular.

http://www.linkedin.com/groups?home=&gid=3885228

We have had some excellent input from Jeff Davis in the past.

Craig