Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Tue, 23 Aug 2005 14:00:15 +0200
From: Oystein.Grovlen@Sun.COM (=?iso-8859-1?q?=D8ystein_Gr=F8vlen?=)
Subject: Re: Derby ClientDriver versus EmbeddedDriver 10.1.1.0 and a question
 about the Eclipse plugin
In-reply-to: <001b01c5a665$9d29b0b0$38577553@DB35TT0J>
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <x1ofu0hgyib4.fsf@atum11.norway.sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8BIT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2
Lines: 18
References: <001b01c5a665$9d29b0b0$38577553@DB35TT0J>

>>>>> "PB" == Piet Blok <pbhome@wanadoo.nl> writes:

    PB> Hi,
    PB> I noticed some different behaviour between Derby EmbeddedDriver and ClientDriver. This was a disappointment, because I wanted to develop a Derby application that may switch between the two drivers.

    PB> Differences I noticed are:

    PB> 1) EmbeddedDriver accepts and uses a Properties object as the second parameter on the connect method. ClientDriver accepts, but does NOT USE the Properties object. A bug?

I guess the problem here is that many of the properties has to be set
when the Derby is started.  In the embedded framework this is done on
the first connect.  In the client/server framework, I guess Derby is
started before the first connect.  Hence, it will be too late to set
the properties.  In my opinion, the ClientDriver should throw an
exception if it is not able to set a property.

-- 
�ystein