Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 4837 invoked from network); 22 Apr 2005 19:21:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Apr 2005 19:21:30 -0000 Received: (qmail 7286 invoked by uid 500); 22 Apr 2005 19:21:49 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 7192 invoked by uid 500); 22 Apr 2005 19:21:48 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 7164 invoked by uid 99); 22 Apr 2005 19:21:48 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from e6.ny.us.ibm.com (HELO e6.ny.us.ibm.com) (32.97.182.146) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 22 Apr 2005 12:21:48 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e6.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j3MJLHcg002727 for ; Fri, 22 Apr 2005 15:21:17 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3MJJq2Q083874 for ; Fri, 22 Apr 2005 15:21:17 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j3MJJq5b020477 for ; Fri, 22 Apr 2005 15:19:52 -0400 Received: from [127.0.0.1] (DMCSDJDT41P.usca.ibm.com [9.72.133.53]) by d01av01.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j3MJJpMu020388 for ; Fri, 22 Apr 2005 15:19:52 -0400 Message-ID: <42694E55.5060500@debrunners.com> Date: Fri, 22 Apr 2005 12:19:49 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev Subject: Upgrade changes committed X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I committed these changes for upgrade Add language upgrade support from 10.0. Add property derby.database.allowPreReleaseUpgrade to allow testing of upgrade code while the code is marked as alpha/beta. Add upgrade check for routines with method signatures to ensure such routines cannot be created while running in soft upgrade mode against 10.0. http://svn.apache.org/viewcvs?rev=164269&view=rev The property derby.database.allowPreReleaseUpgrade addresses a concern Suresh had a while back that the current state of the code would not allow testing of their upgrade code by Derby developers. Setting this property to true allows an 10.0 database to be upgraded with the current trunk code, which is at version 10.1.0.0 alpha. It is not intended for production, indeed with the upgrade policy the upgraded database could not be upgraded to any future 10.1 release, as it is marked as being created by an alpha/beta release. (this code is not specific to any release, but the real version numbers make it easier to explain). Next I'll have commit some test code that isn't part of the current functional tests framework. You run a shell script that runs a java program multiple times using the old release jar files or the new release jar files. E.g. build a 10.0 database, run 10.1 in soft upgrade, run in 10.0 post soft upgrade etc. The output has to be manually checked for FAIL output. The test currently doesn't pass but should once Suresh's upgrade changes at the store level are committed. The test fails when 10.0 is run after soft upgrade and finds new log checksum log records it doesn't understand. At least I'm assuming that's what is going on. :-) Dan.