Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 40901 invoked from network); 8 Dec 2004 22:18:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Dec 2004 22:18:16 -0000 Received: (qmail 244 invoked by uid 500); 8 Dec 2004 22:18:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 133 invoked by uid 500); 8 Dec 2004 22:18:13 -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 99866 invoked by uid 99); 8 Dec 2004 22:18:12 -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 e33.co.us.ibm.com (HELO e33.co.us.ibm.com) (32.97.110.131) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 08 Dec 2004 14:18:10 -0800 Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.195.10]) by e33.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id iB8MI6Dr347110 for ; Wed, 8 Dec 2004 17:18:07 -0500 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay01.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iB8MI6J2231830 for ; Wed, 8 Dec 2004 15:18:06 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id iB8MI5A2004448 for ; Wed, 8 Dec 2004 15:18:05 -0700 Received: from [192.168.1.102] (sig-9-48-116-30.mts.ibm.com [9.48.116.30]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id iB8MI4oQ004412 for ; Wed, 8 Dec 2004 15:18:05 -0700 Message-ID: <41B77D9A.5070903@Sourcery.Org> Date: Wed, 08 Dec 2004 14:18:02 -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: Using Derby as the Jira database References: <200412071816.02361.Joel.Rosi-Schwartz@Etish.org> <41B6FF00.10808@Sourcery.Org> <200412082044.54987.Joel.Rosi-Schwartz@Etish.org> In-Reply-To: <200412082044.54987.Joel.Rosi-Schwartz@Etish.org> 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 Joel Rosi-Schwartz wrote: > Hi Kathy, > > Yes it was the constraint names. I followed the thread "SQL/DDL Limitations > (and DB2)" but it did not seem to reach a conclusion as to whether or not the > size limitations were going to be addressed or when. Do you have any further > feedback on that? > > /joel I think the only thing that was resolved was that it was for the community to decide. I personally think that this type of enhancement request is certainly worthy of a JIRA entry. I looked but I didn't see one. Unfortunately for this particular issue, we cannot turn to the standards. So, now that we have branched, I think it would be an excellent time for some enterprising community member to do the industry research on and present a vote on changes that they: 1) Think are justified and useful. 2) Balance that usefulness with migration ability to and from Derby. 3) Are willing to implement and test. I would probably classify this as a beginner Derby project. since the underlying support for larger limits is there. (But of course nothing is ever as easy as it seems) As to whether it is better to approach the big limit question or just this one really bothersome issue. I have no opinion. Thanks Kathey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBt32aG0h36bFmkocRAuX3AKC0HCHA33bTPUYiD9S5hFM17lqqmgCffdDD 8tSBBgrV4YAHg+XOhOQOoaM= =uq/w -----END PGP SIGNATURE-----