[jira] Commented: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant

["Dyre Tjeldvoll (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12374073 ] 

Dyre Tjeldvoll commented on DERBY-1093:
---------------------------------------

I now have a new patch in my sandbox that includes an updated master file for the new Upgrade test. The new master file shows the new column in the result set returned from getProcedures(). With this new master, the Upgrade test passes. 

I see that 2 of the blocker issues, mentioned in a previous comment, remain open. I guess I should delay uploading a new patch until these issues have been closed, so that the patch doesn't become stale. 

> 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: 10.2.0.0
>     Reporter: Dyre Tjeldvoll
>     Assignee: Dyre Tjeldvoll
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: derby-1093.v1.diff, derby-1093.v1.stat, derbyall_report.txt, upgrade.txt
>
> 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
> PROCEDURE_SCHEM, PROCEDURE_NAME and SPECIFIC_ NAME.
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira