From derby-user-return-5823-apmail-db-derby-user-archive=db.apache.org@db.apache.org Tue Dec 12 10:28:38 2006 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 22056 invoked from network); 12 Dec 2006 10:28:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2006 10:28:37 -0000 Received: (qmail 29935 invoked by uid 500); 12 Dec 2006 10:28:44 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 29529 invoked by uid 500); 12 Dec 2006 10:28:43 -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 29518 invoked by uid 99); 12 Dec 2006 10:28:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 02:28:43 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 02:28:31 -0800 Received: from d1-emea-10.sun.com ([192.18.2.120]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id kBCASAOu008050 for ; Tue, 12 Dec 2006 10:28:10 GMT Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JA500A01P02U900@d1-emea-10.sun.com> (original mail from Bernt.Johnsen@Sun.COM) for derby-user@db.apache.org; Tue, 12 Dec 2006 10:28:10 +0000 (GMT) Received: from localhost ([129.159.112.201]) by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JA50036AP2XLE88@d1-emea-10.sun.com> for derby-user@db.apache.org; Tue, 12 Dec 2006 10:28:09 +0000 (GMT) Date: Tue, 12 Dec 2006 11:28:09 +0100 From: "Bernt M. Johnsen" Subject: Re: unique columns must be nullable ? In-reply-to: Sender: Bernt.Johnsen@Sun.COM To: Derby Discussion Message-id: <20061212102809.GC14663@atum01.norway.sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/signed; boundary=s9fJI615cBHmzTOP; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline References: User-Agent: Mutt/1.5.10i X-Virus-Checked: Checked by ClamAV on apache.org --s9fJI615cBHmzTOP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >>>>>>>>>>>> Xanana Gusmao wrote (2006-12-12 04:08:39): > On this page http://wiki.apache.org/db-derby/HibernateHelp > it says: >=20 > "Hibernate Annotations do not work because Derby does not allow a unique = column > to be nullable" >=20 > Is this (that Derby's unique column must be non-nullable) still true > ? That's still true. UNIQUE constraint on nullable columns is optional feature T591 in the SQL standard and not implemented in Derby. See http://wiki.apache.org/db-derby/SQLvsDerbyFeatures. For a longer discussion of the topic, see http://mail-archives.apache.org/mod_mbox/db-derby-dev/200511.mbox/%3C200511= 02114053.GB7614@atum01.norway.sun.com%3E --=20 Bernt Marius Johnsen, Database Technology Group,=20 Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway --s9fJI615cBHmzTOP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFfoQ4lFBD9TXBAPARAktuAKCSonFfJ2ZY0UCHaFO9Ia8l3q4F1gCfWv1M phY/KZfz060RY21VCHezudA= =GjR+ -----END PGP SIGNATURE----- --s9fJI615cBHmzTOP--