[DERBY-5825] Catch type mismatch of DEFAULT values at DDL time

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.9.1.0
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Release Note Needed, Repro attached
• Bug behavior facts: Deviation from standard
• Assignee: Unassigned
• Reporter: Dag H. Wanvik
• Created: 21/Jun/12 16:32
• Updated: 18/Sep/12 15:23

Description

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

Issue Links

• is related to: DERBY-118 Allow any build-in function as default values in table create for columns.