JDBC Drivers

Thread view:

arN - 04 Jun 2005 07:46 GMT

Hi !

I have to access databases in my app and so use the java.sql package and
its generic interfaces (Connection, ResultSet, ...). The user chooses
the driver according to the database accessed (MySQL and Informix for now).

I just saw that each driver implements the generic interfaces in
concrete classes. Obviously, there is certainly an advantage to use such
specific classes but it is a problem for my code which should work
whatever the driver is.

So, could someone give me more advises on the real advantage of using
these specific classes (speed improvements ? new features ? ...) ?

TIA

--
arN

Reply to this Message

Robert Maas, see http://tinyurl.com/uh3t - 11 Jun 2005 05:27 GMT

> From: arN <pas@demail.svp>
> I have to access databases in my app and so use the java.sql package
[quoted text clipped - 4 lines]
> advantage to use such specific classes but it is a problem for my
> code which should work whatever the driver is.

Why is that a problem for your code? I hope you do the obvious thing of
setting up a properties file which maps the various DB names to the
corresponding driver-name and url so that once the user selects which
RDBS to use the program can automatically load the appropriate driver
and connect via the appropriate url. After you've done that, what's the
problem??

Reply to this Message

JDBC Drivers

Free Magazines