Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <429F1622.7080306@debrunners.com>
Date: Thu, 02 Jun 2005 07:22:26 -0700
From: Daniel John Debrunner <djd@debrunners.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: Use of DriverManager in tests
References: <x1ofacm9vvbr.fsf@atum11.Norway.Sun.COM>
In-Reply-To: <x1ofacm9vvbr.fsf@atum11.Norway.Sun.COM>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

�ystein Gr�vlen wrote:

> When developing a test for Derby-230, I was made aware of that we
> should not use the DriverManager directly, but instead use
> startJBMS().  However, I see some test (e.g.,
> store/backupRestore1.java) that uses the DriverManager when shutting
> down the database and when doing restore.  I am currently working on a
> test for Derby-298 that needs to do the same.  Is it OK to do it this
> way?   What restriction does it impose on which environment the test
> can be run in? 

J2ME does not suport DriverManager. This is because the JDBC JSR169
subset only supports javax.sql.DataSource as the connection mechanism.

I currently have the test suite running under J2ME with about a 50% pass
rate. Many of those failures are due to use of DriverManager, which I
will look at fixing in one way or another.

So at the momeent I would request anyone to minimize use of
DriverManager, but if it is needed then use it.


Dan.