Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 913A710D19 for ; Tue, 1 Jul 2014 12:45:33 +0000 (UTC) Received: (qmail 6883 invoked by uid 500); 1 Jul 2014 12:45:26 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 6846 invoked by uid 500); 1 Jul 2014 12:45:26 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 6752 invoked by uid 99); 1 Jul 2014 12:45:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Jul 2014 12:45:26 +0000 Date: Tue, 1 Jul 2014 12:45:26 +0000 (UTC) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6609) Documentation for SQL features should reflect current standard MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048821#comment-14048821 ] Kim Haase commented on DERBY-6609: ---------------------------------- Thanks, Knut! I will file a patch, then. I will file a separate issue for the ALTER TABLE fixes, since they are not strictly related to this issue. > 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.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)