Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5164

Provide a framework to test upgrade between point releases. Currently, the upgrade testing happens between two major versions.



    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Test
    • None


      DERBY-5121 found a corruption problem caused by triggers in DERBY release A fix for this has been provided in trunk(10.8) and the 10.7 codeline. 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 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


        1. derby5164_patch1_stat.txt
          0.2 kB
          Mamta A. Satoor
        2. derby5164_patch1_diff.txt
          30 kB
          Mamta A. Satoor



            mamtas Mamta A. Satoor
            mamtas Mamta A. Satoor
            0 Vote for this issue
            1 Start watching this issue