Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 67387 invoked from network); 15 Feb 2005 22:22:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Feb 2005 22:22:43 -0000 Received: (qmail 89528 invoked by uid 500); 15 Feb 2005 22:22:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 89494 invoked by uid 500); 15 Feb 2005 22:22:41 -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 89481 invoked by uid 99); 15 Feb 2005 22:22:41 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from matrix.loopback.org (HELO matrix.loopback.org) (217.114.68.34) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 15 Feb 2005 14:22:38 -0800 Received: (qmail 1216 invoked from network); 15 Feb 2005 22:22:30 -0000 Received: from unknown (HELO ?10.0.1.2?) (217.114.68.24) by 0 with SMTP; 15 Feb 2005 22:22:30 -0000 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <421261C4.30605@debrunners.com> References: <421261C4.30605@debrunners.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?thomas_l=F6rtsch?= Subject: Re: SQL identifier lengths Date: Tue, 15 Feb 2005 23:22:29 +0100 To: "Derby Development" X-Mailer: Apple Mail (2.619.2) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Am 15.02.2005 um 21:55 schrieb Daniel John Debrunner: > thomas wrote: > >> Hi, >> >> i tried to use Derby as backend for the DaisyWiki CMS, because i'd >> like >> to get an solution. Currently Daisy only supports MySQL, with >> PostgreSQL >> being in the works. The main problem i ran into was the very >> constrained >> length of SQL identifiers in Derby. >> >> I found this issue on the ToDo-List >> (, Increased SQL >> identifier lengths) and also a discussion-thread which seemed to come >> to >> a consensus that support for longer SQL identifier should be added, >> since it wouldn't break backward-compatibility with DB2 but improve >> support for the SQL-standard >> > 200409.mbox/%3c8D5A122E-09AB-11D9-8965-000A95782782@apache.org%3e>. >> >> >> Although this sounds quite promising to me, it seems like there hasn't >> been a vote taken until now and nobody is working on it. Is this >> correct? Or are there any estimates possible on when a patch will be >> available? Or how much work it would be to develop that patch oneself >> - >> given some experience with java but none with Derby or other >> java-SQL-databases? > > The patch already exists, but it doesn't pass the tests cleanly. Some > work is needed to ensure the test outputs are correct and re-issue the > patch with the changes to the tests. The orignal patch is here: > > http://nagoya.apache.org/eyebrowse/ReadMsg?listName=derby- > dev@db.apache.org&msgNo=1377 > > and my latest comments on it. > > http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200502.mbox/ > %3c42026E14.8000007@debrunners.com%3e > > Dan. so there's hope :-) thanks for the answer, and the great work! ciao thomas . mailto:thomas@stray.net http://stray.net