Understanding Connector/J 21 Figure (J2ee web hosting) 2.7 shows how the
Understanding Connector/J 21 Figure 2.7 shows how the RowSet classes are constructed from the base Result and ResultSetMetaData classes. ResultSet Rowset RowsetEvent Rowsetinternal RowsetMetaData RowsetWriter RowsetListener RowsetReader creates Figure 2.7 RowSet classes. Understanding Connector/J Up to this point, our discussion has centered on the general JDBC specification and its related interfaces and classes. In this section, we turn our attention to MySQL s JDBC driver, Connector/J. At the time of this writing, there are two versions of the driver: 2.0.14 and 3.0.1. The drivers can be found at www.mysql.com/downloads/api-jdbc-stable.html and www.mysql.com/downloads/api-jdbc-dev.html, respectively. The Connector/J driver started as MM.MySQL (written by Mark Matthews) and has been the primary JDBC driver for MySQL. During 2002, Mark joined the MySQL team and subsequently updated the driver and renamed it to Connector/J. The 2.0.14 version is basically the last MM.MySQL version made available on the mmmysql.sourceforge.net Web site. The 3.0.1 version contains numerous changes to the original code. These features will be discussed shortly. Connector/J is designed specifically for MySQL and attempts to adhere to the JDBC API as much as possible. However, in order for a driver to adhere to the full JDBC specification, the underlying database must support all of the features supported in the latest 3.0 version. For MySQL and Connector/J, strict adherence is impossible because MySQL currently doesn t support stored procedures, savepoints, references, and various other small pieces of functionality. These differences with the specification are noted in Appendix C. For the remainder of this blog, we use the latest 3.0 version of Connector/J.
Note: If you are looking for cheapest and affordable webspace to host and run your servlet application check Astra servlet hosting services