db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3423) providesQueryObjectGenerator() should be removed from the DatabaseMetaData implementations
Date Thu, 21 Feb 2008 11:01:19 GMT

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

Knut Anders Hatlen updated DERBY-3423:
--------------------------------------

    Attachment: d3423.diff

Attaching a patch which removes the providesQueryObjectGenerator method and also some other
unused code (unused imports and unused variables) in the DatabaseMetaData implementations.

It also changes the return type of getSchemas(String,String) and getClientInfoProperties()
in the client driver from o.a.d.client.ResultSet to java.sql.ResultSet. This wasn't detected
by the compiler because the class is compiled against JDBC 3.0 libraries, whereas the methods
are defined in JDBC 4.0.

I have started suites.All and derbyall on the patch.

> providesQueryObjectGenerator() should be removed from the DatabaseMetaData implementations
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3423
>                 URL: https://issues.apache.org/jira/browse/DERBY-3423
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Newcomer
>    Affects Versions: 10.4.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>         Attachments: d3423.diff
>
>
> DatabaseMetaData.providesQueryObjectGenerator() was removed from the spec right before
JDBC 4.0 was final, but it's still implemented in Derby. The implementations of this method
should be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message