[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491097
]
A B commented on DERBY-2538:
----------------------------
The patch for DERBY-2488 has been committed and that issue is now resolved. So
if any committers out there have the documentation source set up (I don't;
maybe Laura?), I think DERBY-2538-4.diff can be committed...
Thanks again, Kim.
> Update documentation to describe the expected behavior when a JDBC 4 app
> creates a JDBC 3 datasource.
> -----------------------------------------------------------------------------------------------------
>
> Key: DERBY-2538
> URL: https://issues.apache.org/jira/browse/DERBY-2538
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 10.2.2.0, 10.3.0.0
> Reporter: A B
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: cdevresman89722.html, DERBY-2538-2.diff,
> DERBY-2538-2.zip, DERBY-2538-3.diff, DERBY-2538-3.zip, DERBY-2538-4.diff,
> DERBY-2538-4.zip, DERBY-2538.diff, rdevresman79556.html
>
>
> Based on discussion from DERBY-2488, pages in the Developer's Guide should be
> improved to describe what happens if a JDBC 4 application uses an "old" (JDBC
> 3) datasource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
