Very Computer

When I start the app I use parameters which tell it the URL for the DB
and which driver to use.

I could use one DB object for each database but I think that would get
unweildy with at lesat 2 methods for each object with whose data is
inthe db, e.g. customer, invoice, line item.

I could write one object for each database so I'd have a sybaseCustomer,
  oracleCutomer etc.

Then were do you make the decision? Do I use and object factory that
knows about which of the two to use?

ObjectFActory.getObject("Customer");

Just looking for advice fromthose that have been down the road before.

Thank
jw

IWith my web app, I use Hibernate for all my database/object mapping.  So
when I need to use a different database, I change the properties file for
Hibernate.  Then the system will use the correct database.

Makes writing db objects so easy, and makes the switching between dbs a
little easier.

J

http://www.asg.sc.edu/pdf/DatabaseIndependence.pdf

Good luck!

I have a app that I want to point to Oracle today and Sybasee Tomorrow.

Both dbs have a stored proc named GetClientList which returns a result
set to the client. The way the Oracle does it and the way Sybase does it
are totaly differrent in how they pass back the result set so that you
can't just change JDBC drivers. Someplace in the app I have to write
database specific, Oracle, Sybase whatever, code for methods with the
same name that return the same ResultSet. It's only a couple of lines of
code different but it still means that any db accessor that that calls
an SP that returns a Result set needs to be database specific.

My question is what is the best way to, or more probably what are the
trades offs in the different ways, to do this?

jw