Database - JDBC, Java Server Pages, and MySQL - Discussion

Sun proposed only-jdbcodbcbridge driver.

Jdbc native driver-dbvendor.

Jdbcnet protocol driver-middleware servers.

Jdbc native protocol-db vendor.

JDBC-ODBC :

1) Required client side Installation.
2) Plate Dependent.
3) Performance Overhead.

Native API :

1) Required client side Installation.
2) Plate Dependent.
3) Performance Overhead.

Network Protocol:

1) Support more than on DB.
2) Less Performance.
3) 100% Pure JAVA Driver.
4) Plate independent.

Native Protocol:

1) DB dependent.
2) high Performance.
3) 100% Pure JAVA Driver.
4) Plate independent.

JDBC-ODBC bridge driver.

Native-API driver (partially java driver).

Network Protocol driver (fully java driver).

Thin driver (fully java driver).

I know only 1 driver JDBCODBC. I don't know other drivers.

Four JDBC driver types:
__________________

1. JDBC-ODBC bridge -> It employs ODBC driver to connect to the database.

2. Native API Driver -> It uses the client-side libraries for the database.

3. Network Protocol Driver (Middleware Driver) -> makes use of middle tier between the calling program and the database.

4. Database-Protocol Driver ( Pure Java Driver) -> converts JDBC calls directly into a vendor-specific database protocol.

->Source(wiki).

hi nice