Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 22672 invoked from network); 16 Dec 2004 21:52:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Dec 2004 21:52:38 -0000 Received: (qmail 58416 invoked by uid 500); 16 Dec 2004 21:52:37 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 58360 invoked by uid 500); 16 Dec 2004 21:52:36 -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 58318 invoked by uid 99); 16 Dec 2004 21:52:36 -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 over.ny.us.ibm.com (HELO over.ny.us.ibm.com) (32.97.182.150) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 16 Dec 2004 13:49:47 -0800 Received: from e1.ny.us.ibm.com ([192.168.1.101]) by pokfb.esmtp.ibm.com (8.12.10/8.12.10) with ESMTP id iBGIuYjK019048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Dec 2004 13:56:34 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.10/8.12.10) with ESMTP id iBGIrNb1025724 for ; Thu, 16 Dec 2004 13:53:23 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iBGIr8qZ282236 for ; Thu, 16 Dec 2004 13:53:23 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id iBGIr8IN018758 for ; Thu, 16 Dec 2004 13:53:08 -0500 Received: from [192.168.1.102] (sig-9-48-109-123.mts.ibm.com [9.48.109.123]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id iBGIr7Xk018728 for ; Thu, 16 Dec 2004 13:53:07 -0500 Message-ID: <41C1D992.2090007@Sourcery.Org> Date: Thu, 16 Dec 2004 10:53:06 -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 Development Subject: Re: [PATCH] Change all Identifier Limitations to 128 References: <41BCAF05.7090006@hug.cx> <41C1AD94.5010801@hug.cx> In-Reply-To: <41C1AD94.5010801@hug.cx> X-Enigmail-Version: 0.85.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-2.apache.org 1.6.2 0/1000/N -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp Hug wrote: > this patch changes maximum length of column names, index/contraint > names, cursor names and schema names to 128 and keeps MaxUserNameLength > at 30. > it also fixes the metadata to return correct values I have a few questions about this change. 1) For a change like this I would think there would be some functional tests needed and of course documentation changes. So how do they come to be? It would be good to have the functional tests go in with the change and have someone at least signed up to do the doc changes. Otherwise how do we keep track? 2) What are the implications of this change on soft upgrade? 3)If we change the limits what do we do about this line in our charter? "And it also means developers can later migrate to other databases if they so choose." Is it still appropriate? Thanks Kathey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwdmSG0h36bFmkocRAmceAJ95p/QfuYz3UljEnlLZchCMZR0NywCeOmJ+ ozDu/NRK162zg7Ut+LzoXSo= =2AhR -----END PGP SIGNATURE-----