Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 65699 invoked from network); 30 Mar 2006 00:43:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Mar 2006 00:43:36 -0000 Received: (qmail 59621 invoked by uid 500); 30 Mar 2006 00:43:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 59592 invoked by uid 500); 30 Mar 2006 00:43:35 -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 59583 invoked by uid 99); 30 Mar 2006 00:43:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Mar 2006 16:43:35 -0800 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.145] (HELO e5.ny.us.ibm.com) (32.97.182.145) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Mar 2006 16:43:34 -0800 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e5.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k2U0h8hq013475 for ; Wed, 29 Mar 2006 19:43:08 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k2U0gw6F107124 for ; Wed, 29 Mar 2006 19:42:58 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k2U0gqtT023900 for ; Wed, 29 Mar 2006 19:42:52 -0500 Received: from [127.0.0.1] (sig-9-48-116-70.mts.ibm.com [9.48.116.70]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k2U0gnqn023788 for ; Wed, 29 Mar 2006 19:42:52 -0500 Message-ID: <442B2986.1070403@sbcglobal.net> Date: Wed, 29 Mar 2006 16:42:46 -0800 From: Kathey Marsden User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: [jira] Updated: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions. References: <1733524392.1143644387310.JavaMail.jira@ajax> <442AC280.6020709@sun.com> <87zmj9kqsb.fsf@sun.com> In-Reply-To: <87zmj9kqsb.fsf@sun.com> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Knut Anders Hatlen wrote: >" > > >I'll summarize my understanding of these two issues > > [snip very good explanation] >As you suggested, the client could invoke the SQL directly. This would >however cause some problems: > > - if there is a bug in a metadata query, it is not enough to upgrade > the server, you would also have to upgrade all the clients. > > - if the server changes the name of a system table or a column in a > system table, old clients will be broken. > > > Another problem is that the metadata queries currently use non-supported syntax. Changing these to use supported syntax, such as Mamta did when adding optimizer directives would mean that the old non-supported syntax would have to stay in the server. One more thing not mentioned here was that Satheesh for 1120/1124 added some version dependent metadata queries, which were necessary for soft upgrade because with the full v10.2 upgrade, system columns needed to be accessed for the metadata queries that were not available on soft upgrade. That seemed like a reasonable approach to soft upgrade. Once all the infrastructure gets firmed up, it would be good to have some information on the Wiki about how maintain metadata queries. It is good to see it getting addressed. Kathey