JEP 170: JDBC 4.2
|Status||Closed / Delivered|
|JSRs||114 MR, 221 MR|
|Discussion||jdbc dash spec dash discuss at openjdk dot java dot net|
|Endorsed by||Mark Reinhold|
|Depends||JEP 150: Date & Time API|
Minor enhancements to JDBC to improve usability and portability
Improve the ability to leverage new data types and continue to make improvements in areas that have been requested by JDBC application programmers and driver vendors.
Changes under consideration for JDBC 4.2 include:
Add a generic setter/update method to
CallableStatementto support new data types such as those being defined in JSR 310.
REF_CURSORsupport for CallableStatement.
DataSourceproperties for a Java EE environment.
DatabaseMetaData.getIndexInfoto provide new columns for
PAGESwhich return a long value.
Add a new
DatabaseMetamethod to return the logical maximum size for a LOB.
Additional clean up of the spec as needed.
Changes will be mostly additions to existing interfaces.
The JCK will need to tests added for any concrete methods/classes, e.g.,
PreparedStatement.setObject(int pos, Object val, SQLType type).
Risks and Assumptions
The primary risk of this change is that any change affecting method type-inference has the potential for backwards incompatibility.
JSR 310, the new Date and Time API (JEP 150).
Compatibility: Minimal - Additional methods will be added to existing interfaces, but that only affects JDBC drivers. Existing JDBC applications will continue to run unmodified.
Documentation: Additional updates to the spec and the javadoc spec
JCP: A Maintenance Release of JSR 221, as done for JDBC 4.1, with a 30-day review period