Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 85609 invoked from network); 28 Feb 2008 22:33:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Feb 2008 22:33:32 -0000 Received: (qmail 57517 invoked by uid 500); 28 Feb 2008 22:33:27 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 57492 invoked by uid 500); 28 Feb 2008 22:33:27 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 57483 invoked by uid 99); 28 Feb 2008 22:33:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2008 14:33:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.19.6] (HELO sineb-mail-1.sun.com) (192.18.19.6) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2008 22:32:40 +0000 Received: from fe-apac-04.sun.com (fe-apac-04.sun.com [192.18.19.175] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1SMWs4M022614 for ; Thu, 28 Feb 2008 22:32:54 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JWY00L01Y960500@mail-apac.sun.com> (original mail from Anurag.Shekhar@Sun.COM) for derby-dev@db.apache.org; Fri, 29 Feb 2008 06:32:48 +0800 (SGT) Received: from [192.168.1.110] ([122.171.0.249]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JWY00415ZYOAJ41@mail-apac.sun.com> for derby-dev@db.apache.org; Fri, 29 Feb 2008 06:32:48 +0800 (SGT) Date: Fri, 29 Feb 2008 04:02:45 +0530 From: Anurag shekhar Subject: unique constraint and db2 compatibility tests Sender: Anurag.Shekhar@Sun.COM To: derby-dev@db.apache.org Message-id: <47C7368D.10808@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.14pre (X11/20071023) X-Virus-Checked: Checked by ClamAV on apache.org After enabling unique constraint on nullable fields db2 compatibility tests are failing because they expect failure while creating unique constraint over null able fields. For now I have modified the out file (Attached separately in DERBY-3330, db2Compatibility.diff ) Is it right thing to do ? or Shall I modify the test itself to stop testing unique constraint over null able fields ? thanks anurag