Examining the JDBC (Subdomain web hosting) Interface 15 A developer can

Examining the JDBC Interface 15 A developer can also work with standardization by using metadata supplied from the database. Many times, a database will return information in the form of metadata, indicating whether it supports specific features. Examining the JDBC Interface Now that we know what JDBC is, where it came from, and its place in a typical system, let s turn our attention to the interfaces used to create the driver. Figure 2.3 shows how all of the core interfaces in the specification are designed to work together. Statement Prepared Statement Callable Statement ResultSet ResultSetResultSet Connection DriverManager Connector/J MySQL Figure 2.3 The Core JDBC API structure. As we mentioned earlier, the specification is broken up into two different packages: the Core API and the Optional API. The Core API is implemented in the java.sql package. In this section, we look at the interfaces available in the specification (although we don t indicate here whether Connector/J supports the functionality that can be found in Appendix C). The java.sql Package You can find this information both in Appendix C and in the section Understanding Connector/J later in this chapter. The interfaces specifically defined
Note: If you are looking for cheap and inexpensive provider to host and run your tomcat application check Actions tomcat hosting services

Comments are closed.