db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6609) Documentation for SQL features should reflect current standard
Date Mon, 16 Jun 2014 14:34:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032469#comment-14032469
] 

Knut Anders Hatlen commented on DERBY-6609:
-------------------------------------------

I think it sounds reasonable to remove the ones that are N/A in 2011 entirely. At least if
we don't implement them at all.

Seems like there are some that have just changed the feature id. For example, 99 and 2003
had F691 "Collation and translation". That feature is no longer listed in 2011. Instead, there
is a new feature F690 "Collation support". I suppose we could just change the id and description
of that feature, and keep saying "partial". Or we could list them both. I don't have any strong
preferences.

One new feature on trunk that I didn't mention in my first comment, is
  T211-05 Ability to specify a search condition that shall be True before the trigger is invoked.
which I think describes the WHEN clause in CREATE TRIGGER.

> Documentation for SQL features should reflect current standard
> --------------------------------------------------------------
>
>                 Key: DERBY-6609
>                 URL: https://issues.apache.org/jira/browse/DERBY-6609
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Kim Haase
>         Attachments: DERBY-6609.diff, DERBY-6609.stat, DERBY-6609.zip
>
>
> We document Derby as an SQL-92 database. This standard is now very old, and we should
describe how Derby conforms to the most current standard (SQL:2011). Knut Anders Hatlen listed
the relevant features in a comment to DERBY-6605. 
> This will involve at a minimum replacing the "Derby support for SQL-92 features" topic
(http://db.apache.org/derby/docs/10.10/ref/rrefsql9241891.html) with a new one that describes
Derby's support for current features, with notes as needed indicating when the support is
partial. Only features Derby supports, fully or partially, should be listed. We should state
that features not listed are not supported.
> The information would be taken from http://wiki.apache.org/db-derby/SQLvsDerbyFeatures
(which currently goes only through the 2003 standard). Listing the Feature IDs in the documentation
would also be helpful. 
> Other topics should be changed as needed. For example, is the term "SQL92Identifier"
still correct?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message