Introduction of java jdbc
- 2. Before JDBC, ODBC API was the database API to associate and execute question with the database. Be that as it may, ODBC API utilizes ODBC driver which is composed in C dialect (i.e. stage needy and unsecured). That is the reason Java has characterized its own API (JDBC API) that utilizations JDBC drivers (written in Java dialect).
- 3. What is API Programming interface (Application programming interface) is a report that contains portrayal of the considerable number of elements of an item or programming. It speaks to classes and interfaces that product projects can take after to speak with each other. An API can be made for applications, libraries, working frameworks, and so forth .. Propelled JAVA Training in Marathahalli bangalore
- 4. There are 4 sorts of JDBC drivers 1. JDBC-ODBC connect driver 2. Native-API driver (mostly java driver) 3. Network Protocol driver (completely java driver) 4. Thin driver (completely java driver)
- 5. 1) The ODBC driver should be introduced on the customer machine. 2) Native-API driver The Native API driver utilizes the customer side libraries of the database. The driver changes over JDBC technique calls into local calls of the database API. It is not composed totally in java.
- 6. Favorable position: performance updated than JDBC- ODBC connect driver. Burden: The Native driver should be introduced on the every customer machine: The Vendor customer library should be introduced on customer machine.
- 7. 3) Network Protocol driver : The Network Protocol driver utilizes middleware (application server) that proselytes JDBC calls straightforwardly or in a roundabout way into the merchant particular database convention. It is completely composed in java. Preferred standpoint: No customer side library is required in light of utilization server that can perform many errands like examining, stack adjusting, logging and so on.
- 8. Detriments: Network bolster is required on customer machine. 1) JDBC-ODBC bridge driver The JDBC-ODBC bridge driver uses ODBC driver to connect to the database. The JDBC-ODBC bridge driver converts JDBC method calls into the ODBC function calls. This is now discouraged because of thin driver.
- 9. Advantages: easy to use. can be easily connected to any database. Disadvantages: Performance degraded because JDBC method call is converted into the ODBC function calls. The ODBC driver needs to be installed on the client machine.
- 10. 2) Native-API driver The Native API driver uses the client-side libraries of the database. The driver converts JDBC method calls into native calls of the database API. It is not written entirely in java. Advantage: performance upgraded than JDBC-ODBC bridge driver. Disadvantage: The Native driver needs to be installed on the each client machine. The Vendor client library needs to be installed on client machine.
- 11. 3) Network Protocol driver The Network Protocol driver uses middleware (application server) that converts JDBC calls directly or indirectly into the vendor-specific database protocol. It is fully written in java. Advantage: No client side library is required because of application server that can perform many tasks like auditing, load balancing, logging etc.
- 12. Disadvantages: Network support is required on client machine. Requires database-specific coding to be done in the middle tier. Maintenance of Network Protocol driver becomes costly because it requires database-specific coding to be done in the middle tier.
- 13. 4) Thin driver The thin driver converts JDBC calls directly into the vendor-specific database protocol. That is why it is known as thin driver. It is fully written in Java language. Advantage: Better performance than all other drivers. No software is required at client side or server side. Disadvantage: Drivers depends on the Database.