[
https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3456:
----------------------------------
Attachment: derby-3456-Tests.diff
derby-3456v3.diff
Description of derby-3456v3.diff
I have regenerated the patch with latest trunk. In my last patch
(v2) I had made a mistake, I was skipping creating new index if the
existing was unique index, while setting the key part to null able. It should
be other ways. I have fixed that in this patch.
Description of derby-3456-Tests.diff
This has Test Cases for
1. Soft and Hard upgrade
2. Index tests (created while running older version and soft upgrade and used
during other phases).
3. New test case to test setting a column participating in unique constraint to
null.
4. Updated lang/altertable.sql and altertable.out for setting column
participating in unique constraint to null. (Modified to expect success)
I haven't finished running tests with these two patch.
> 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.0.0
> Environment: all
> Reporter: Anurag Shekhar
> Assignee: Anurag Shekhar
> Attachments: altertable.diff, derby-3456-Tests.diff,
> derby-3456v1.diff, derby-3456v2.diff, derby-3456v3.diff, setnulltest.diff,
> upgradetests.diff, upgradetests_v2.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
