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] Updated: (DERBY-1243) Modify ODBCMetaDataGenerator to use the JDBC4 version of metadata queires as input
Date Tue, 19 Sep 2006 15:27:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1243?page=all ]

Rick Hillegas updated DERBY-1243:
---------------------------------

    Fix Version/s: 10.2.2.0
                       (was: 10.2.1.0)

Moving to 10.2.2.0.

> Modify ODBCMetaDataGenerator to use the JDBC4 version of metadata queires as input
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-1243
>                 URL: http://issues.apache.org/jira/browse/DERBY-1243
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.2.1.0
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>             Fix For: 10.2.2.0
>
>
> ODBCMetadataGenerator transforms jdbc metadata queries into ODBC equivalents. JDBC 4
introduces new versions of getProcedures() and getProcedureColumns(), but the old version
of the queries had to be kept because they are used as input to ODBCMetadataGenerator. Since
the old queries are really redundant, we should modify ODBCMetadataGenerator to use the new
queries as input, and remove the old queries from metadata.properties.

-- 
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