[
https://issues.apache.org/jira/browse/DERBY-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662029#action_12662029
]
Knut Anders Hatlen commented on DERBY-4006:
-------------------------------------------
Or actually... It seems like the defaultNode argument (with declared type
Object) passed to ColumnDefinitionNode.init() is an UntypedNullConstantNode,
but the instance variable defaultNode is declared to be of type DefaultNode,
and it cannot hold an UntypedNullConstantNode, so it should be null in this
case.
Adding a boolean sounds like a good idea. +1
> ALTER COLUMN ... WITH DEFAULT NULL does not change the default
> --------------------------------------------------------------
>
> Key: DERBY-4006
> URL: https://issues.apache.org/jira/browse/DERBY-4006
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3,
> 10.4.2.0
> Reporter: Knut Anders Hatlen
> Assignee: Bryan Pendleton
>
> Reported on derby-user.
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200901.mbox/%[email protected]%3e
> ij> create table t (x varchar(5) default 'abc');
> 0 rows inserted/updated/deleted
> ij> alter table t alter column x with default null;
> 0 rows inserted/updated/deleted
> ij> insert into t values default;
> 1 row inserted/updated/deleted
> ij> select * from t;
> X
> -----
> abc
> 1 row selected
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
