SQL99 feature list

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: SQL99 feature list
Date: 2002-06-14 14:59:01
Message-ID: 3D0A04B5.11391299@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

As you probably know, SQL99 has dropped the rather useless
categorizations of "basic", "intermediate", and "advanced" SQL
compliance and instead lists a large number of labeled features. I've
put these into an appendix for the docs (not yet committed to cvs).

The list is organized as a (for now) three column table, with "Feature",
"Description", and "Comment" as the three column headers. This is a
relatively long list, covering several printed pages.

So, a question: should I list all features in the same table, with the
comment field indicating if something is not (yet) supported, or should
I split the features into two tables for supported and unsupported
features? The former keeps all of the information together if someone is
looking something up by feature, and the latter reduces the number of
required comments and makes it easier to see the complete list of
supported features.

- Thomas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew Tedder 2002-06-14 15:12:33 Big Test Environment Feature
Previous Message Dave Page 2002-06-14 14:48:42 Re: Language Comments