[
https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575410#action_12575410
]
army edited comment on DERBY-3456 at 3/5/08 8:44 AM:
----------------------------------------------------
> Is it ok if I create a new issue for 2 and 3 ? They are actually independent
> issue caused by DERBY-3330 and creating a separate issues for them
> will allow this (3456) issue to remain unblocked.
Sure, that's fine with me :) In fact, if you'd like to put all 3 of the
"shared backing index" issues I mentioned above into one new Jira issue, that
seems reasonable (and perhaps "cleaner" from an incremental development
approach) to me....
was (Author: army):
> Is it ok if I create a new issue for 2 and 3 ? They are actually
independent
> issue caused by DERBY-3330 and creating a separate issues for them
> will allow this (3456) issue to remain unblocked.
Sure, that's fine with me :)
> 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, derby-3456v4.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.
