Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 28716 invoked from network); 25 Apr 2006 14:45:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Apr 2006 14:45:32 -0000 Received: (qmail 93241 invoked by uid 500); 25 Apr 2006 14:45:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 93180 invoked by uid 500); 25 Apr 2006 14:45:18 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 92650 invoked by uid 99); 25 Apr 2006 14:45:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2006 07:45:15 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.43] (HELO brmea-mail-2.sun.com) (192.18.98.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2006 07:45:13 -0700 Received: from phys-gadget-1 ([129.156.85.171]) by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id k3PEiq91002928 for ; Tue, 25 Apr 2006 08:44:53 -0600 (MDT) Received: from conversion-daemon.gadget-mail1.uk.sun.com by gadget-mail1.uk.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IYA003018TN59@gadget-mail1.uk.sun.com> (original mail from Knut.Hatlen@Sun.COM) for derby-dev@db.apache.org; Tue, 25 Apr 2006 15:44:50 +0100 (BST) Received: from khepri19 (khepri19.Norway.Sun.COM [129.159.112.231]) by gadget-mail1.uk.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IYA005468YBZH@gadget-mail1.uk.sun.com> for derby-dev@db.apache.org; Tue, 25 Apr 2006 15:44:37 +0100 (BST) Date: Tue, 25 Apr 2006 16:44:35 +0200 From: Knut Anders Hatlen Subject: Re: [jira] Updated: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions. In-reply-to: To: derby-dev@db.apache.org Message-id: Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/22.0.50 (usg-unix-v) References: <1733524392.1143644387310.JavaMail.jira@ajax> <442AC280.6020709@sun.com> <87zmj9kqsb.fsf@sun.com> <442AED77.3040902@Sourcery.Org> <44315CBC.7090604@sun.com> <44316351.6070503@Sourcery.Org> <443184EF.9000500@sbcglobal.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Knut Anders Hatlen writes: > Kathey Marsden writes: > >> I am a bit fuzzy on this still after I reread the thread for DERBY-1107 >> a few times. I was wondering if someone could summarize? Has an >> upgrade strategy been defined for metadata? > > I don't think we defined a strategy, but we seem to agree on: > > 1) It is possible to fix it (without time travel) when the need > arises. > > 2) If we want to fix it before the need arises, it is acceptable to > drop and recreate stored prepared statements on every maintenance > release. > > 3) Metadata changes should be avoided in point releases. > >> Could someone who >> understands it put it on the Wiki? > > I can start on a wiki page tomorrow. If someone wants do to it > earlier, just go ahead! Sorry that it took so long. I have put up a wiki page on http://wiki.apache.org/db-derby/MetadataUpgrade and linked to it from the front page. Feel free to add, remove or change whatever you would like. -- Knut Anders