Return-Path: 
 <derby-user-return-5392-apmail-db-derby-user-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-user-archive@www.apache.org
Received: (qmail 2996 invoked from network); 16 Oct 2006 11:07:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 16 Oct 2006 11:07:54 -0000
Received: (qmail 71652 invoked by uid 500); 16 Oct 2006 11:07:53 -0000
Delivered-To: apmail-db-derby-user-archive@db.apache.org
Received: (qmail 71379 invoked by uid 500); 16 Oct 2006 11:07:52 -0000
Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-user-help@db.apache.org>
list-unsubscribe: <mailto:derby-user-unsubscribe@db.apache.org>
List-Post: <mailto:derby-user@db.apache.org>
List-Id: <derby-user.db.apache.org>
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Delivered-To: mailing list derby-user@db.apache.org
Received: (qmail 71368 invoked by uid 99); 16 Oct 2006 11:07:52 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 04:07:52 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of chas66@gmail.com designates
 64.233.182.189 as permitted sender)
Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 04:07:49 -0700
Received: by nf-out-0910.google.com with SMTP id p77so1849434nfc
        for <derby-user@db.apache.org>; Mon, 16 Oct 2006 04:07:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=MrQydgo6hZL9YmimDkYbYAhhCyYT91QuvxS3KKAfSoXOINaHQX+G6DI5yP+o55J0/SBEIS2pDHZk9ATX4hAiuRXN/8wxB2LVF2OiF+EEwj61XJddcYZtckvna7o45TDsR8QC6Lh+ZJKZl8cxuV6uzEhw8SBgqHW1L/UH5X7SHdg=
Received: by 10.82.114.3 with SMTP id m3mr903468buc;
        Mon, 16 Oct 2006 04:07:25 -0700 (PDT)
Received: by 10.82.151.12 with HTTP; Mon, 16 Oct 2006 04:07:25 -0700 (PDT)
Message-ID: <375e8d880610160407s9646f6dm812201c848f089bc@mail.gmail.com>
Date: Mon, 16 Oct 2006 21:07:25 +1000
From: "Chris Barham" <cbarham@pobox.com>
Sender: chas66@gmail.com
To: "Derby Discussion" <derby-user@db.apache.org>, msegel@segel.com
Subject: Re: Is it Possible to Turn off Referential Constraints for a DBUNIT
 Load?
In-Reply-To: <20061016042205.A8FB84B962@dbrack01.segel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <375e8d880610121732n3ab7b2bbq6b06d1027ab842e5@mail.gmail.com>
	 <20061016042205.A8FB84B962@dbrack01.segel.com>
X-Google-Sender-Auth: fb66edd3fbe2d029
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 10/16/06, Michael Segel <msegel@segel.com> wrote:
<snip>
> [mjs]
> If you think about it, you don't have to *have* referential constraints on a
> table. They are placed there for a reason.
>
> So why do you want to load data that may violate them?

Because DBUnit is a very convenient way to put a database into a known
state, except when references become a problem for the flat file
nature of the source.  No other reason; I am not a mysql fanboy,
merely trying to get stuff done.

Chris