JDBC-Implementation of Connection,Resultset,Statement

[Raghunath.ek]

Hi all,

In JDBC We use Connection,Resultset,Statement..etc.
All these are interfaces, but we are using it..
My Question is:
1.Where is the implementation of these interfaces?
2. We will load the JDBC driver in the first step.. Instead can we put the driver class in class path? Why loading class using Class.forName()
3.What is the difference between using JDBC driver and datasource?

Any information about the question will be appreciated..

[bhargavig]

Hi all,

In JDBC We use Connection,Resultset,Statement..etc.
All these are interfaces, but we are using it..
My Question is:
1.Where is the implementation of these interfaces?
2. We will load the JDBC driver in the first step.. Instead can we put the driver class in class path? Why loading class using Class.forName()
3.What is the difference between using JDBC driver and datasource?

Any information about the question will be appreciated..

Hi,

Eventhough the Connection,Statement and ResultSet are interfaces the implementation for these will exist in the driver classes taht we are losding while connection creation.

we can put the driver class in the class path, ifwe do like tis each java class will take this which is not necessary.

Only for Type1 driver we create datasource,as there is no direct interaction between jdbc and odbc, but this is not the case with Oracle (Type4) driver.

I hope this may give u some clarification.

Regards,
Bhargavi.

[softvijay]

hi all, in jdbc we use connection,resultset,statement..etc. All these are interfaces, but we are using it.. My question is: 1.where is the implementation of these interfaces? 2. We will load the jdbc driver in the first step.. Instead can we put the driver class in class path? why loading class using class.forname() 3.what is the difference between using jdbc driver and datasource? any information about the question will be appreciated..

hi, using jdbc driver makes database url, user, password bound to your java codes. Now imagine a situation when ur database url, username & password becomes something different, in that senerio u need to update all the codes which make the use of hardcore connection object. Also when u use jdbc driver u make physical connection to database everytime u want to connect. Using datasource, (1) your application is portable because all the url, user, password can be specifed in descriptor file (web.xml) (2) by default datasoruce uses pool connection, so when u request for connection, one already in pool is connected (no physical connection) and when u close a connection, it returns to pool. Vj