From ddlutils-dev-return-524-apmail-db-ddlutils-dev-archive=db.apache.org@db.apache.org Wed Jan 04 22:36:57 2006 Return-Path: Delivered-To: apmail-db-ddlutils-dev-archive@www.apache.org Received: (qmail 38849 invoked from network); 4 Jan 2006 22:36:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jan 2006 22:36:53 -0000 Received: (qmail 86166 invoked by uid 500); 4 Jan 2006 22:36:44 -0000 Delivered-To: apmail-db-ddlutils-dev-archive@db.apache.org Received: (qmail 86147 invoked by uid 500); 4 Jan 2006 22:36:44 -0000 Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ddlutils-dev@db.apache.org Delivered-To: mailing list ddlutils-dev@db.apache.org Received: (qmail 86136 invoked by uid 99); 4 Jan 2006 22:36:44 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 14:36:44 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of tomdzk@gmail.com designates 64.233.182.196 as permitted sender) Received: from [64.233.182.196] (HELO nproxy.gmail.com) (64.233.182.196) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 14:36:43 -0800 Received: by nproxy.gmail.com with SMTP id p77so1123930nfc for ; Wed, 04 Jan 2006 14:36:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RljweEFxkN8YdOEFvlk9CTVOfnM8HoKf8kdfpEFFreZzfwpUi+HhzttDyPy0VpOGT68uXYMwF37SnOP+F2MxTxIpnhO32atY7oa8/XJu8GNiese4WHmgLwoqesVKYk3VmQOWPcStluXpp68SmgeeKLCIzttHDH/b4jIm6BuPhV4= Received: by 10.48.207.6 with SMTP id e6mr682915nfg; Wed, 04 Jan 2006 14:36:22 -0800 (PST) Received: by 10.48.250.15 with HTTP; Wed, 4 Jan 2006 14:36:22 -0800 (PST) Message-ID: <224f32340601041436v4ffb6044w135b4855506797ad@mail.gmail.com> Date: Wed, 4 Jan 2006 23:36:22 +0100 From: Thomas Dudziak To: ddlutils-dev@db.apache.org Subject: Re: svn commit: r365722 - /db/ddlutils/trunk/src/test/org/apache/ddlutils/io/ConstraintsTestBase.java In-Reply-To: <43BC4B3A.1090302@mvdb.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060103195302.45696.qmail@minotaur.apache.org> <43BB0FDE.4060609@mvdb.net> <224f32340601031605w194eb352w88a23e5f6d21b69f@mail.gmail.com> <43BC06EF.3020102@mvdb.net> <224f32340601040949x6298fecdjad2019bcdb65d3e1@mail.gmail.com> <43BC104E.7090109@mvdb.net> <224f32340601041024p60319312r7492b0a6cee74f68@mail.gmail.com> <43BC411D.8090109@mvdb.net> <224f32340601041405s66a3e6c6ia5540d0d5aa2af80@mail.gmail.com> <43BC4B3A.1090302@mvdb.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 1/4/06, Martin van den Bemt wrote: > > This might be useful for tests for the database alteration > > functionality (which IMO we still have to provide though perhaps not > > for the 1.0). > > This is the part I am very interested in and using most of the time actua= lly :) To expand on that a bit more: I think we need (at least for after the 1.0) two more sets of tests: (1) Database alteration. Similar to the datatype/constraint tests, we start with a model and create it in the database. Then we change the original model in one aspect, e.g. add a column, or change the size of a column or whatever. Then we ask the platform to alter the database and check what happens. To make the tests database independent, it is probably useful to compare the model read-back after the initial creation - adjusted according to the intentioned change - with the model read-back after the alteration. Or we could check the alteration SQL, though then the tests are database specific. (2) Reading and using of live databases. Here we should create the database using database-specific SQL (e.g. a test per native type as well as the constraints, default values etc.), then read it back, check this model and perhaps also insert some stuff and get it back (as the datatype tests do). But honestly, I think we should do this after the 1.0 because this looks like a lot of work ... > No problem. Curious how much you can get running (currently have 18 failu= res and 3 errors) on the > datatypestest. I just discovered that MySql returns a default value for columns specified as not null, even if there was no default value spec. Strange database ... Tom