db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby
Date Tue, 04 Oct 2005 16:27:49 GMT
    [ http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331279 ] 

Daniel John Debrunner commented on DERBY-587:

The document says that EmbeddedDataSource40 extends EmbeddedDataSource30, but there is no
such class in Derby.
In fact this EmbeddedDataSource40 looks like it has to become part of the public api, which
means a shift in Derby from a single class for JDBC 2.0 and JDBC 3.0, to applications having
to select a specific DataSource for JDBC 4.0.
Not sure this is a problem for this check in, but it might be something that needs to be resolved
before a Derby release is made that  supports JDBC 4.0. E.g. if the DataSource doesn't change
in JDBC 5.0 then do applications still need to load EmbeddedDataSource40, possibly leading
to confusion?

One minor issue with the patch, the new constant in JVMInfo for JDK 1.6 has the comment aka
J2SE 5.0 which is the same as JDK 1.5. Is that true?

> Providing JDBC 4.0 support for derby
> ------------------------------------
>          Key: DERBY-587
>          URL: http://issues.apache.org/jira/browse/DERBY-587
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Versions:
>     Reporter: V.Narayanan
>     Assignee: V.Narayanan
>     Priority: Minor
>      Fix For:
>  Attachments: jdbc4.0.sxw, jdbc40.diff, jdbc40.stat

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message