db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant
Date Wed, 15 Mar 2006 11:38:41 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12370497 ] 

Dyre Tjeldvoll commented on DERBY-1093:

This is a bit more tricky than I first imagined. The first thing to note is that the modified
query in metadata.properties must be given a new name (key) in order to ensure that the new
query gets used after an upgrade, (see DERBY-1107). But the query named getProcedures is also
used as input to generate queries for ODBC. It turns out that the JDBC 4.0 version of getProcedures
is NOT compatible with ODBC since it adds SPECIFIC_NAME which has no counter part in ODBC.
This leaves us with 3 alternatives:

1) Keep both the old and the new version of the query. This will leave the ODBC queries as
before, but makes metadata.properties more cluttered. 
2) Replace the existing query with a new one with a new name, and rewrite the ODBC logic to
use the new query name as input. Will result in additional non-standard columns in ODBC.
3) Modify the ODBCQueryGenerator so that the extra column gets removed in the ODBC version
of the query. Will work but is more work, and potentially more risky?

What do people think?

> Make DatabaseMetaData.getProcedures() JDBC4 compliant
> -----------------------------------------------------
>          Key: DERBY-1093
>          URL: http://issues.apache.org/jira/browse/DERBY-1093
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC, Newcomer
>     Versions:
>     Reporter: Dyre Tjeldvoll
>     Assignee: Dyre Tjeldvoll
>     Priority: Minor
>      Fix For:

> JDBC 4.0 requires that the result set returned from getProcedures must contain a new
column SPECIFIC_NAME"and that the result set must be ordered by
> The SYSALIASES table already has a column called SPECIFICNAME, so it should only be necessary
to modify the query in metadata.properties.

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