Hi Øystein
I filed a Jira issue (Derby-530) on the Properties issue. I included a code
fragment illustrating a workaround for the problem. I see no reason why the
ClientDriver cannot do the same internally.
However, there are some other issues: actually, I do not exactly understand
yet the difference between connection attributes and database or other
attributes. The manuals name a couple of connection attributes, but are
these the only attributes? I have to do a lot more studying the manuals and
experimenting before I feel comfortable to comment on your remarks.
Piet Blok
----- Original Message -----
From: ""Øystein Grøvlen"" <[EMAIL PROTECTED]>
To: "Derby Discussion" <[email protected]>
Sent: Tuesday, August 23, 2005 2:00 PM
Subject: Re: Derby ClientDriver versus EmbeddedDriver 10.1.1.0 and a
question about the Eclipse plugin
"PB" == Piet Blok <[EMAIL PROTECTED]> 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
