[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
Derby Info: [Patch Available, Release Note Needed] (was: [Release Note
Needed, Patch
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Derby Info: [Patch Available, Release Note Needed]
provide support for unique constraint over
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: db2Compatibility-v2.diff
description of db2Compatibility-v2.diff
removed test
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v11.diff
Description of patch (derby-3330v11.diff)
Now the backing
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: db2Compatibility.diff
db2Compatibility.diff
diff file to update
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v12.diff
derby-3330v12.diff
fixed indentation issues and added comment
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v13.diff
changes in derby-3330v13.diff
1. replaced uniqueWhenNotNull
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
do you know why the master for dml019 changed?
Index:
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
I am running a set of tests on the v9 patch and will post results when they are
done. I am
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v10.diff
Changes in this (derby-3330v10.diff) patch since
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
Attachment: derbyall_report.txt
report of diffs on ibm15 jvm running on xp laptop using
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
From running the v9 patch on ibm15 jvm against a windows XP laptop I got 1
failure in the junit
Army wrote:
I haven't been following this discussion at all, but for what it's
worth, this same sort of question came up in the context of
DERBY-3299. I went with the simple approach of dropping the old index
and creating the new one, so some logic for that kind of thing is now
in the 10.4
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v9.diff
I have removed hard upgrade code from derby-3330v9.diff. Now the
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: UniqueConstraint_Implementation_V3.html
updated hard upgrade section.
provide
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v7.diff
This page include the code to scan multiple slot/page if the
Mike Matrigali wrote:
In what situation will it be necessary to run hard upgrade. My
understanding was that only new software would create these new
types of indexes. All old index behavior was to remain the same
and thus would not need the new functionality. So all existing
unique indexes
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v8.diff
In this patch (derby-3330v8.diff) I have modified upgrade
Why are you upgrading the backing indexes of existing unique
constraints, those that exist should only be on non-nullable columns
so should not need to be changed. I have not read through the new
code yet, but I assume also that new constraints on non-nullable columns
also don't use the new
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
please update your implementation spec to include your plan for hard upgrade.
Once this is done
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
comment on implementation details:
While creating the unique constraint null checking is now
Existing unique constraint will have only non nullable columns but it is
possible
to make columns null able (using statement alter table table name alter
column column name null) .
Making columns null able isn't allowed on a column participating in
unique constraint
but as a part of this patch
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: UniqueConstraint_Implementation_V2.html
Updated version Implementation Details.
I would rather see the upgrade in this case take place when the alter
happens rather than creating the non-nullable index up front with null
checks, allowing unique indexes that never have this to enjoy the
performance possible when the null checking is not necessary. This
would mean either
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to convert from old index type to new
index type.
I haven't been following this discussion at all, but for what it's
worth, this same sort of question came up in the
Army wrote:
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to convert from old index type to new
index type.
I haven't been following this discussion at all, but for what it's
worth, this same sort of question came up
Anurag shekhar wrote:
Army wrote:
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to convert from old index type to new
index type.
I haven't been following this discussion at all, but for what it's
worth, this same
Mike Matrigali wrote:
Anurag shekhar wrote:
Army wrote:
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to convert from old index type to new
index type.
I haven't been following this discussion at all, but for what
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v6.diff
This patch includes hard upgrade (Upgrade test from 10.3.1.4 and
In what situation will it be necessary to run hard upgrade. My
understanding was that only new software would create these new
types of indexes. All old index behavior was to remain the same
and thus would not need the new functionality. So all existing
unique indexes should continue to throw
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
o although unlikely a legal state for a leaf page is to have a control row, but
no other rows.
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v5.diff
This patch includes following changes since v4
1. Fixed
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: UniqueConstraint_Implementation.html
Attaching the implementation documents. I
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: BTreeController.diff
Thanks Mike in taking time to explain the nuances of locking
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
At this point you should somehow document the implementation that you are
planning to support the
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: FunctionalSpec_DERBY-3330-V2.html
Fixed typos in functional specs.
provide
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
comments of functional spec/hard upgrade section:
It says:
During had upgrade existing backing
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3330:
--
here are some initial comments on the derby-3330v4.diff patch
overall:
o almost unique, doesn't
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330-testcase.diff
derby-3330v4.diff
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: FunctionalSpec_DERBY-3330.html
Revised functional spec from derby-2212
provide
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v3.diff
This patches fixes all the failures in test suite cased by this
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330v2.diff
I have done some cleanup in this patch. This patch also includes
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-3330:
--
Attachment: derby-3330.diff
I am running the tests and will be updating the patch based on the
43 matches
Mail list logo
