[jira] [Updated] (DERBY-5164) Provide a framework to test upgrade between point releases. Currently, the upgrade testing happens between two major versions.

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5164:
-----------------------------------

    Comment: was deleted

(was: I do not forsee any further code changes related to backing out DERBY-1482 changes so I think it should be safe to resolve this issue so we don't have any blockers for 10.8 release.

The right fix for DERBY-1482 can go in as part of DERBY-1482 even after 10.8 release is out. Those changes can then be made available as next point release of 10.8 and since at the time of upgrade, the trigger SPSes get marked invalid, any changes made for DERBY-1482 will get automatically picked up. )

> Provide a framework to test upgrade between point releases. Currently, the upgrade testing happens between two major versions.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5164
>                 URL: https://issues.apache.org/jira/browse/DERBY-5164
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.0.2.1, 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.2.1, 10.7.1.1
>            Reporter: Mamta A. Satoor
>
> DERBY-5121 found a corruption problem caused by triggers in DERBY release 10.7.1.1 A fix for this has been provided in trunk(10.8) and the 10.7 codeline. 10.7.1.1 database upgrade to any one of these 2 codelines will fix the triggers causing the corruption. I was able to write upgrade tests for 10.8 codeline but not for 10.7 codeline. The reason for this can be found in the comment insdie org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeRun:baseSuite 
>     * Changes are only added if the old version is older than
>     * then version the changes represent. Thus Changes10_2
>     * is not added if the old database (upgrade from) is already
>     * at 10.2, since Changes10_2 is intended to test upgrade
>     * from an older version to 10.2.
> The last line in the comment "since Changes10_2 is intended to test upgrade from an older version to 10.2." is not really true specifically for DERBY-5121. We want to test upgrade from 10.7.1.1 to next point release/codeline of 10.7.
> Providing this framework should not be too hard. I just wanted to create this jira so we can keep track of the issue.
> More information on this issue can be found at http://mail-archives.apache.org/mod_mbox/db-derby-dev/201103.mbox/%3CAANLkTinYKkO0nef+8gM4oJmRE0jnzC-qbXy3ZN4_e3oG@mail.gmail.com%3E

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira