Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 32338 invoked from network); 30 May 2006 18:21:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 May 2006 18:21:39 -0000 Received: (qmail 42233 invoked by uid 500); 30 May 2006 18:21:38 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 42209 invoked by uid 500); 30 May 2006 18:21:37 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 42198 invoked by uid 99); 30 May 2006 18:21:37 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 May 2006 11:21:37 -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.1.36] (HELO gmpea-pix-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 May 2006 11:21:37 -0700 Received: from d1-emea-04.sun.com (d1-emea-04.sun.com [192.18.2.114] (may be forged)) by gmpea-pix-1.sun.com (8.12.9/8.12.9) with ESMTP id k4UILAg5003950 for ; Tue, 30 May 2006 19:21:14 +0100 (BST) Received: from conversion-daemon.d1-emea-04.sun.com by d1-emea-04.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J0300D018Q5K200@d1-emea-04.sun.com> (original mail from Bernt.Johnsen@Sun.COM) for derby-user@db.apache.org; Tue, 30 May 2006 19:21:10 +0100 (BST) Received: from localhost (180.80-203-115.nextgentel.com [80.203.115.180]) by d1-emea-04.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J0300951CB8ZZ70@d1-emea-04.sun.com>; Tue, 30 May 2006 19:21:10 +0100 (BST) Date: Tue, 30 May 2006 20:20:48 +0200 From: "Bernt M. Johnsen" Subject: Re: "generated by default" question In-reply-to: <200605301309.19884.derby@segel.com> Sender: Bernt.Johnsen@Sun.COM To: Derby Discussion , derby@segel.com Message-id: <20060530182048.GB21158@localhost.localdomain> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/signed; boundary=uAKRQypu60I7Lcqm; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline References: <20060530144043.52834243A4@dbrack01.segel.com> <200605301309.19884.derby@segel.com> User-Agent: Mutt/1.5.9i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >>>>>>>>>>>> Michael Segel wrote (2006-05-30 13:09:19): > The issue that we see is that Derby barfs when it hits a row that > was inserted without using the identity value, and Derby doesn't > know how to generate the next identity value. >=20 > That sir, is a bug. > And no, the SQL 2000 spec, as presented in this discussion does not concu= r=20 > with how derby is implementing their auto sequence generation. I have not studied this well enough to conclude wether Derby's current behaviour is compliant with the SQL 2000 spec or not. But there is nothing in the Derby charter that requires Derby to be SQL 2000 compliant, so if you're right, Derby is not compliant, but that's no bug, that's a feature, especially if it's documented. > So, when will either Sun or IBM fix this? ;-) --=20 Bernt Marius Johnsen, Database Technology Group,=20 Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfI0AlFBD9TXBAPARAp86AJoCwVwDa/LIId0X2ai8Wo8smHPc3wCfQBHB 3PgARNUWYZL8Q6AS2y5vRYI= =PlpS -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--