JDBC Class Abstraction

From: Sameer Utrankar <sameeru_at_exchange.ml.com>
Date: Tue, 09 Nov 1999 10:57:03 -0500
Message-ID: <3828444F.CA19CD8C@exchange.ml.com>

This is a design related question and not really a programming issue.

Is it good to:
(1) Use JDBC directly in the application ?
(2) Build a DBAccess layer on top of JDBC and ask programmers to use
the layer ?

(1) gives you quicker solution because no extra effort of layer
building, need for programmers to know JDBC, Lot of work if JDBC API changes and app needs to be changed.
(2) upfront effort to build the layer and easy to switch (?) if JDBC API
changes down the road.

I know Object Oriented Pundits will prefer to chose (2) and argue such as what if database changes from Oracle to Sybase, JDBC API changes etc. But taking a practical view how often such things happen in a company ? How often JDBC API is likely to change ? Will the change be such that it's not backward compatible ?

Just trying to find what's the best approach for a new Java project. Any help ? Received on Tue Nov 09 1999 - 09:57:03 CST