You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/06/12 11:32:01 UTC

[jira] [Commented] (DERBY-6609) Documentation for SQL features should reflect current standard

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

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

Copying the list of relevant SQL:2011 features from DERBY-6605:

F200 TRUNCATE TABLE statement
F851 <order by clause> in subqueries
F852 Top-level <order by clause> in views
F855 Nested <order by clause> in <query expression>
F856 Nested <fetch first clause> in <query expression>
F857 Top-level <fetch first clause> in <query expression>
F858 <fetch first clause> in subqueries
F859 Top-level <fetch first clause> in views
F860 dynamic <fetch first row count> in <fetch first clause>
F861 Top-level <result offset clause> in <query expression>
F862 <result offset clause> in subqueries
F863 Nested <result offset clause> in <query expression>
F864 Top-level <result offset clause> in views
F865 dynamic <offset row count> in <result offset clause>

Additionally, the following features have been added to trunk for 10.11:

F312 MERGE statement
F313 Enhanced MERGE statement
F314 MERGE statement with DELETE branch
F492 Optional table constraint enforcement
F721 Deferrable constraints
F261-01 Simple CASE 
F262 Extended CASE expression
F263 Comma-separated predicates in simple CASE expression


> 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
>
> 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)