GeeCON Prague 2014*
The moose likes Object Relational Mapping and the fly likes Hibernate + sun's jdbcodbc  Driver Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Hibernate + sun Watch "Hibernate + sun New topic
Author

Hibernate + sun's jdbcodbc Driver

Mr. C Lamont Gilbert
Ranch Hand

Joined: Oct 05, 2001
Posts: 1170

Can I use the sun built in jdbcodbc driver with Hibernate? can I use Hibernate with this driver and a database that does not support transacttions such as the MS JET Database Engine?


Thanks
Ghulam Rashid
Ranch Hand

Joined: Jan 14, 2002
Posts: 278
Are you mean, Type I driver (jdbc dbc..... ) which requires client configuration also? If so, then I tried once but could not do that. Then I switched to type3/4 driver then it worked for me. but, still I am not sure whether Hibernate supports this or not.
Mr. C Lamont Gilbert
Ranch Hand

Joined: Oct 05, 2001
Posts: 1170

sun's jdbc.odbc driver is type 1? I thought surely it was 3 at least!?
Ghulam Rashid
Ranch Hand

Joined: Jan 14, 2002
Posts: 278
Types of JDBC technology drivers
JDBC technology drivers fit into one of four categories:

Type-1
A JDBC-ODBC bridge provides JDBC API access via one or more ODBC drivers. Note that some ODBC native code and in many cases native database client code must be loaded on each client machine that uses this type of driver. Hence, this kind of driver is generally most appropriate when automatic installation and downloading of a Java technology application is not important. For information on the JDBC-ODBC bridge driver provided by Sun, see JDBC-ODBC Bridge Driver.

Type-2
A native-API partly Java technology-enabled driver converts JDBC calls into calls on the client API for Oracle, Sybase, Informix, DB2, or other DBMS. Note that, like the bridge driver, this style of driver requires that some binary code be loaded on each client machine.

Type-3
A net-protocol fully Java technology-enabled driver translates JDBC API calls into a DBMS-independent net protocol which is then translated to a DBMS protocol by a server. This net server middleware is able to connect all of its Java technology-based clients to many different databases. The specific protocol used depends on the vendor. In general, this is the most flexible JDBC API alternative. It is likely that all vendors of this solution will provide products suitable for Intranet use. In order for these products to also support Internet access they must handle the additional requirements for security, access through firewalls, etc., that the Web imposes. Several vendors are adding JDBC technology-based drivers to their existing database middleware products.

Type-4
A native-protocol fully Java technology-enabled driver converts JDBC technology calls into the network protocol used by DBMSs directly. This allows a direct call from the client machine to the DBMS server and is a practical solution for Intranet access. Since many of these protocols are proprietary the database vendors themselves will be the primary source for this style of driver. Several database vendors have these in progres
 
GeeCON Prague 2014
 
subject: Hibernate + sun's jdbcodbc Driver