db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3010) WITH DEFAULT value documentation is too liberal
Date Wed, 15 Aug 2007 15:45:31 GMT
WITH DEFAULT value documentation is too liberal
-----------------------------------------------

                 Key: DERBY-3010
                 URL: https://issues.apache.org/jira/browse/DERBY-3010
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1,
10.0.2.0
            Reporter: Dag H. Wanvik
            Priority: Minor


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.


Mime
View raw message