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: pass (asf.osuosl.org: local policy)
From: "Peter Neubauer" <pnb@scancoin.se>
Message-Id: <57225B99BCBEFB4CA1E00E323596972D3B5EF6@amanda.ad.local>
Date: Wed, 24 Aug 2005 08:18:32 +0200
To: derby-dev@db.apache.org
Subject: =?Iso-8859-1?Q?SV:_Driver30_where_is_it_used=3F?=
Message-ID: <57225B99BCBEFB4CA1E00E323596972D3B5EF6@amanda.ad.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Dan,
Thanks for the fast reply,
> Applications should not acceess the Driver20 or Driver30 classes
> directly, the public api is EmbeddedDriver and DriverManager (e.g.
> DriverManager.getConnection).
> =

> Driver20 and Driver30 do not handle the network URL, only the =

> embedded,
> thus they are required in derby.jar.
I understand that, but it seems that "jdbc:derby://localhost:9001/journal=
db;create=3Dtrue" is returning the Driver30 for client applications that =
have derby.jar in their classloader. I'm not sure of the specification bu=
t maybe the problem is that from the specification POV the embedded URL s=
yntax "jdbc:derby:journaldb;create=3Dtrue" and the above new network clie=
nt syntax are the same? =

In that case there is a problem that might be surface not only for me, si=
nce it seems that from the JDBC specification, the first driver accepting=
 a given connection URL has to be returned to the asking client.

Not sure this makes sense, just want to stress the point that http://www.=
solarmetric.com/Support/Newsgroups/news/article.php?id_article=3D%3Cde5ek=
5%24ecp%241%40solarmetric.netmar.com%3E&grp_id=3D1 should not be able to =
happen since I used the network URL and you are saying the Driver30 is on=
ly handling embedded URLs?

/peter