[
https://issues.apache.org/jira/browse/DERBY-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2487:
----------------------------------
I have not done a system catalog upgrade, but here are some places to look.
I assume the right thing would be to disable the feature in soft upgrade. I
think this is usually done in parser or the procedure call, whatever applies
best for the feature. It looks like
update statistics procedure should have this, and has been added to upgrade
tests.
For pointers on adding system catalogs maybe you can look at code in
java/engine/org/apache/derby/impl/sql/catalog/DD_Version.java. There looks
like a few versions
in the past that dealt with new catalogs:
if (fromMajorVersionNumber <= DataDictionary.DD_VERSION_DERBY_10_3)
{
// Add new system catalogs created for roles
bootingDictionary.upgradeMakeCatalog(
tc, DataDictionary.SYSROLES_CATALOG_NUM);
}
if (fromMajorVersionNumber <= DataDictionary.DD_VERSION_DERBY_10_1)
{
// add catalogs 1st, subsequent procedure adding may depend on
// catalogs.
// Add new system catalogs created for grant and revoke
bootingDictionary.upgradeMakeCatalog(
tc, DataDictionary.SYSTABLEPERMS_CATALOG_NUM);
bootingDictionary.upgradeMakeCatalog(
tc, DataDictionary.SYSCOLPERMS_CATALOG_NUM);
bootingDictionary.upgradeMakeCatalog(
tc, DataDictionary.SYSROUTINEPERMS_CATALOG_NUM);
}
It looks like the 10.5 update statistics feature laid the test groundwork for
10.5 upgrade testing
to the upgrade tests, so you should just be able to add appropriate test cases:
java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests
> Enhance Derby with EXPLAIN Functionality
> ----------------------------------------
>
> Key: DERBY-2487
> URL: https://issues.apache.org/jira/browse/DERBY-2487
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.2.2.0
> Reporter: Felix Beyer
> Assignee: Bryan Pendleton
> Priority: Minor
> Attachments: Derby physical XPLAIN schema.png,
> incorporateTrunkChanges.diff, RSProtocolNew.pdf, rts.xls, small logical
> xplain schema.pdf, startRegressionTest.diff, startRegressionTest.diff,
> updateRegressionTests.diff, updateRegressionTests.diff, usage.txt,
> xplain_patch_v1.txt, xplainClasses.pdf
>
>
> This enhancement extends Derby with EXPLAIN functions. Users want to have
> more feedback than they`re getting with the current RuntimeStatistics
> facility. This extension is based on the
> RuntimeStatistics/ResultSetStatistics functions / classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.