[
https://issues.apache.org/jira/browse/DERBY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533388
]
Kim Haase commented on DERBY-3010:
----------------------------------
Thanks for doing this research, Dag. I will work on this and post a revised
patch, incorporating any additional changes that come in in the meantime.
> 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
>
>
> 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.
