[
https://issues.apache.org/jira/browse/DERBY-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5825:
--------------------------------------
Issue & fix info: Release Note Needed,Repro attached (was: Release Note
Needed)
Urgency: Normal
Affects Version/s: 10.9.1.0
Labels: derby_triage10_10 (was: )
> Catch type mismatch of DEFAULT values at DDL time
> -------------------------------------------------
>
> Key: DERBY-5825
> URL: https://issues.apache.org/jira/browse/DERBY-5825
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.9.1.0
> Reporter: Dag H. Wanvik
> Labels: derby_triage10_10
>
> Derby postpones checking values in DEFAULT clauses to DML time, cf this
> example:
> create table t(c varchar(2) default 'foo')
> insert into t values default
> According to the standard [1], an error should result at create table time.
> Derby throws an error only at insert time above. Similarly for other types.
> Cf also discussion in DERBY-118.
> Cf also comments in ColumnDefinitionNode#defaultTypeIsValid:
> "We'll check this at insertion time; see Beetle 5585 regarding the
> need to move that check to here instead of waiting until insert
> time."
> We should implement correct type checking of the DEFAULT values given at DDL
> time.
> [1]
> https://issues.apache.org/jira/browse/DERBY-118?focusedCommentId=13397195&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13397195
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
