db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1768) Remove JDBC 4.0 RowId classes
Date Mon, 28 Aug 2006 17:52:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1768?page=comments#action_12431023 ] 
Knut Anders Hatlen commented on DERBY-1768:

EmbedRowId is in derby.jar because RowIdNotImplementedTest and Driver40 have a direct reference
to it. The client class is not in derbyclient.jar. Since the classes have no functionality
at all, I don't see much point in leaving them in the codeline. You could always restore them
from subversion later.

> Remove JDBC 4.0 RowId classes
> -----------------------------
>                 Key: DERBY-1768
>                 URL: http://issues.apache.org/jira/browse/DERBY-1768
>             Project: Derby
>          Issue Type: Improvement
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: rowid.diff, rowid.stat
> JDBC 4.0 introduced the java.sql.RowId interface. Derby has implemented this interface
both in the client driver and the embedded driver, but the methods only throw java.lang.UnsupportedOperationException,
and an application has no way to get a RowId object. To reduce the footprint, these unused
classes should be removed.

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


View raw message