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] [Comment Edited] (DERBY-6609) Documentation for SQL features should reflect current standard
Date Mon, 16 Jun 2014 13:28:01 GMT

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

Knut Anders Hatlen edited comment on DERBY-6609 at 6/16/14 1:26 PM:
--------------------------------------------------------------------

-The wiki page is only missing one mandatory feature from SQL:2011 part 2:-

-T631 IN predicate with one list element-

-Derby does seem to support that feature.-

\[update: That feature was actually on the wiki too, but with the wrong feature id. Has been
corrected on the wiki now.\]

I found the following optional features were missing on the wiki:

B035 Non-extended descriptor names
F054 TIMESTAMP in DATE type precedence list
F122 Enhanced diagnostics management
F123 All diagnostics
F200 TRUNCATE TABLE statement
F202 TRUNCATE TABLE: identity column restart option
F263 Comma-separated predicates in simple CASE expression
F313 Enhanced MERGE statement
F314 MERGE statement with DELETE branch
F382 Alter column data type
F383 Set column not null clause
F384 Drop identity property clause
F385 Drop column generation expression clause
F386 Set identity column generation clause
F394 Optional normal form specification
F403 Partitioned join tables
F492 Optional table constraint enforcement
F690 Collation support
F762 CURRENT_CATALOG
F763 CURRENT_SCHEMA
F841 LIKE_REGEX predicate
F842 OCCURRENCES_REGEX function
F843 POSITION_REGEX function
F844 SUBSTRING_REGEX
F845 TRANSLATE_REGEX
F846 Octet support in regular expression operators
F847 Nonconstant regular expressions
F850 Top-level <order by clause> in <query expression>
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>
F866 FETCH FIRST clause: PERCENT option
F867 FETCH FIRST clause: WITH TIES option
S098 ARRAY_AGG
S301 Enhanced UNNEST
S401 Distinct types based on array types
S402 Distinct types based on distinct types
S403 ARRAY_MAX_CARDINALITY
S404 TRIM_ARRAY
T021 BINARY and VARBINARY data types
T022 Advanced support for BINARY and VARBINARY data types
T023 Compound binary literals
T024 Spaces in binary literals
T043 Multiplier T
T044 Multiplier P
T101 Enhanced nullability determination
T177 Sequence generator support: simple restart option
T178 Identity columns: simple restart option
T180 System-versioned tables
T181 Application-time period tables
T213 INSTEAD OF triggers
T285 Enhanced derived column names
T341 Overloading of SQL-invoked functions and SQL-invoked procedures
T472 DESCRIBE CURSOR
T495 Combined data change and retrieval
T502 Period predicates
T521 Named arguments in CALL statement
T522 Default values for IN parameters of SQL-invoked procedures
T614 NTILE function
T615 LEAD and LAG functions
T616 Null treatment option for LEAD and LAG functions
T617 FIRST_VALUE and LAST_VALUE functions
T618 NTH_VALUE function
T619 Nested window functions
T620 WINDOW clause: GROUPS option

Derby supports some, but not all, of the new, optional features. I haven't gone through all
of them yet and checked which are supported.


was (Author: knutanders):
The wiki page is only missing one mandatory feature from SQL:2011 part 2:

T631 IN predicate with one list element

Derby does seem to support that feature.

I found the following optional features were missing on the wiki:

B035 Non-extended descriptor names
F054 TIMESTAMP in DATE type precedence list
F122 Enhanced diagnostics management
F123 All diagnostics
F200 TRUNCATE TABLE statement
F202 TRUNCATE TABLE: identity column restart option
F263 Comma-separated predicates in simple CASE expression
F313 Enhanced MERGE statement
F314 MERGE statement with DELETE branch
F382 Alter column data type
F383 Set column not null clause
F384 Drop identity property clause
F385 Drop column generation expression clause
F386 Set identity column generation clause
F394 Optional normal form specification
F403 Partitioned join tables
F492 Optional table constraint enforcement
F690 Collation support
F762 CURRENT_CATALOG
F763 CURRENT_SCHEMA
F841 LIKE_REGEX predicate
F842 OCCURRENCES_REGEX function
F843 POSITION_REGEX function
F844 SUBSTRING_REGEX
F845 TRANSLATE_REGEX
F846 Octet support in regular expression operators
F847 Nonconstant regular expressions
F850 Top-level <order by clause> in <query expression>
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>
F866 FETCH FIRST clause: PERCENT option
F867 FETCH FIRST clause: WITH TIES option
S098 ARRAY_AGG
S301 Enhanced UNNEST
S401 Distinct types based on array types
S402 Distinct types based on distinct types
S403 ARRAY_MAX_CARDINALITY
S404 TRIM_ARRAY
T021 BINARY and VARBINARY data types
T022 Advanced support for BINARY and VARBINARY data types
T023 Compound binary literals
T024 Spaces in binary literals
T043 Multiplier T
T044 Multiplier P
T101 Enhanced nullability determination
T177 Sequence generator support: simple restart option
T178 Identity columns: simple restart option
T180 System-versioned tables
T181 Application-time period tables
T213 INSTEAD OF triggers
T285 Enhanced derived column names
T341 Overloading of SQL-invoked functions and SQL-invoked procedures
T472 DESCRIBE CURSOR
T495 Combined data change and retrieval
T502 Period predicates
T521 Named arguments in CALL statement
T522 Default values for IN parameters of SQL-invoked procedures
T614 NTILE function
T615 LEAD and LAG functions
T616 Null treatment option for LEAD and LAG functions
T617 FIRST_VALUE and LAST_VALUE functions
T618 NTH_VALUE function
T619 Nested window functions
T620 WINDOW clause: GROUPS option

Derby supports some, but not all, of the new, optional features. I haven't gone through all
of them yet and checked which are supported.

> 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