[
https://issues.apache.org/jira/browse/DERBY-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner closed DERBY-1731.
----------------------------------------
> Add warning to Derby docs that the JDBC 4.0 support is based upon the
> proposed final draft of JSR 221 and might change in subsequent releases.
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1731
> URL: https://issues.apache.org/jira/browse/DERBY-1731
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.2.1.6, 10.2.2.0
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Fix For: 10.2.1.6, 10.2.2.0
>
> Attachments: derby-1731-refGuide_v01.diff
>
>
> While JDBC 4.0 does not require any warning statement (see DEBRY-1639) it
> would be good for Derby to have such a statement.
> I think we want to freedom to match JDBC 4.0 final spec in a future 10.2
> release, a warning would help this, including stating that
> applications written to JDBC 4.0 might need to be modified and re-compile to
> work successfully.
> ------------------------------------------------
> Sample release note added here. This can be wordsmithed on the website
> depending on the actual discrepancies, if any, between the GA version of Java
> SE 6 and the beta version with which Derby 10.2 is compatible.
> PROBLEM:
> Derby 10.2 exposes an early access implementation of JDBC4 interfaces.
> SYMPTOM:
> When an application runs on Java SE 6, you may see problems like the
> following. These are just examples of the kinds of problems you may see. The
> actual discrepancies will be listed here.
> 1) Abstract method errors when calling methods on Derby objects which
> implement interfaces from the java.sql and javax.sql packages.
> 2) Unpredictable results when using constants declared in the java.sql and
> javax.sql packages.
> CAUSE:
> Derby 10.2 was built and tested using an early access (late beta) version of
> the JDBC4 interfaces. It is possible that the JDBC4 spec will change between
> that beta version and the actual GA of Java SE 6. In that case, Derby 10.2
> will not completely satisfy the GA version of the JDBC4 spec.
> SOLUTION:
> The first maintenance release of Derby 10.2 will align Derby with the GA
> version of Java SE 6.
> WORKAROUND:
> Do not run your application on Java SE 6 if your application needs to use
> JDBC features whose specification changed between the time that Derby 10.2
> was built and the GA of Java SE 6. To use these features, you will have to
> wait until the first maintenance release of Derby 10.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
