db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (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.
Date Mon, 21 Aug 2006 22:27:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1731?page=comments#action_12429555 ] 
            
Rick Hillegas commented on DERBY-1731:
--------------------------------------

Where should we put this disclaimer? We could put in in the Reference Guide in the "JDBC Reference"
section.

> 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: http://issues.apache.org/jira/browse/DERBY-1731
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.2.1.0, 10.2.2.0
>            Reporter: Daniel John Debrunner
>             Fix For: 10.2.1.0, 10.2.2.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message