[
https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-3456.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.1.3
Assignee: Anurag Shekhar
Actually, looking at the current code, it appears to me that the issue of the
message was resolved after all.
(there's a switch happening based on DataDictionary.DD_VERSION_DERBY_10_4 in
ModifyColumnNode).
So, this can just be resolved.
I also noted that there *is* no release note for DERBY-3330 or its
subtasks...Probably because DERBY-3330 was closed *after* release of 10.4 into
which the functionality went, the check for existence of release note was not
carried out. But there's no need for a release note on behalf of this subtask.
> Allow removing not null from collumns particpating in unique constraint.
> ------------------------------------------------------------------------
>
> Key: DERBY-3456
> URL: https://issues.apache.org/jira/browse/DERBY-3456
> Project: Derby
> Issue Type: Sub-task
> Components: SQL, Store
> Affects Versions: 10.4.1.3
> Environment: all
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Fix For: 10.4.1.3
>
> Attachments: altertable.diff, derby-3456-Tests.diff,
> derby-3456-Tests_v2.diff, derby-3456v1.diff, derby-3456v2.diff,
> derby-3456v3.diff, derby-3456v4.diff, derby-3456v5.diff, setnulltest.diff,
> upgradetests.diff, upgradetests_v2.diff
>
>
> Enable alter table to change a column that participates in a unique
> constraint to allow nulls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
