You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "A B (JIRA)" <ji...@apache.org> on 2007/04/24 17:45:16 UTC

[jira] Resolved: (DERBY-2538) Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.

     [ https://issues.apache.org/jira/browse/DERBY-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A B resolved DERBY-2538.
------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0
       Derby Info:   (was: [Patch Available])

Thank you for the commit, Laura.

> 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
>             Fix For: 10.3.0.0
>
>         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.