[
https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-2538:
-----------------------------
Attachment: DERBY-2538-2.zip
DERBY-2538-2.diff
Attaching DERBY-2538-2.diff and DERBY-2538-2.zip, which incorporate Army's
suggested changes (I hope).
M src/devguide/rdevresman79556.dita
M src/devguide/cdevresman89722.dita
M src/adminguide/cadminappsxawthdriver.dita
M src/adminguide/cadminnsdatasources.dita
Please let me know if any additional changes would be helpful.
> 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.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.
