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 Wed, 02 Jul 2014 09:54:24 GMT

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

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

Thanks, Kim. The #6 patch looks good. +1 to commit.

In my description of the support for F382, I failed to mention that VARCHAR FOR BIT DATA was
supported, so we might want to add that.

I noticed that the #5 patch sometimes said "Part 2 (Core SQL)". Core SQL is actually the set
of mandatory features in part 2 and 11 plus some optional features. The name of Part 2 is
Foundation, so I think it would be more correct to say "Part 2 (Foundation)".

I've filed DERBY-6644 to implement the standard syntax for set/drop not null. It looks like
an easy fix, so hopefully we can remove that comment soon.



> 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
>            Assignee: Kim Haase
>         Attachments: DERBY-6609-2.diff, DERBY-6609-2.zip, DERBY-6609-3.diff, DERBY-6609-3.diff,
DERBY-6609-3.stat, DERBY-6609-3.zip, DERBY-6609-3.zip, DERBY-6609-4.diff, DERBY-6609-4.stat,
DERBY-6609-4.zip, DERBY-6609-5.diff, DERBY-6609-5.stat, DERBY-6609-5.zip, DERBY-6609-6.diff,
DERBY-6609-6.stat, DERBY-6609-6.zip, 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