Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 75217 invoked from network); 9 Oct 2007 21:02:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2007 21:02:47 -0000 Received: (qmail 10110 invoked by uid 500); 9 Oct 2007 21:02:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 10078 invoked by uid 500); 9 Oct 2007 21:02:34 -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 10053 invoked by uid 99); 9 Oct 2007 21:02:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2007 14:02:34 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2007 21:02:44 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 54A0E714241 for ; Tue, 9 Oct 2007 14:01:54 -0700 (PDT) Message-ID: <2086967.1191963714344.JavaMail.jira@brutus> Date: Tue, 9 Oct 2007 14:01:54 -0700 (PDT) From: "Kim Haase (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3010) WITH DEFAULT value documentation needs improvement In-Reply-To: <21810128.1187192731653.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-3010: ----------------------------- Attachment: DERBY-3010-2.zip DERBY-3010-2.diff Thank you, Dag! Here is a revised patch. I changed "should" to "must", and I also noticed that in the second bullet item, "SCHEMA or SQLID" actually should have been "CURRENT SCHEMA or CURRENT SQLID" -- at least I think so. Hope this is okay. > WITH DEFAULT value documentation needs improvement > -------------------------------------------------- > > Key: DERBY-3010 > URL: https://issues.apache.org/jira/browse/DERBY-3010 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.4.0.0 > Reporter: Dag H. Wanvik > Assignee: Kim Haase > Priority: Minor > Attachments: defaultConstantExpression.txt, DERBY-3010-2.diff, DERBY-3010-2.zip, DERBY-3010.diff, DERBY-3010.zip > > > The descrition in the reference manual for DEFAULT value option, leads > one to assume that the value may be specified as a constant > expression, e.g. as (0), whereas Derby (in compliance with the SQL > standard) is more restrictive. > In the specifications for CREATE and ALTER TABLE (rrefsqlj81859.dita > and rrefsqlj30540.dita), "ConstantExpression" is used: > column-definition: > : > [ [ WITH ] DEFAULT { ConstantExpression | NULL } > | generated-column-spec ] > : > This non-terminal symbol is explained in rrefsqlj30540.dita: > "For the definition of a default value, a ConstantExpression is an > expression that does not refer to any table. It can include constants, > date-time special registers, current schemas, users, and null." > Perhaps one could change the name to ConstantValue and explain it > as: > "For the definition of a default value, a ConstantValue means literals, > date-time special registers, current schemas, users, and null." > Or better, one could be more explicit and spell out the options in > more detail.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.