[ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12370659 ]
Dyre Tjeldvoll commented on DERBY-1093: --------------------------------------- I was just thinking about removing the old queries when ODBCMetadataGenerator has been changed so that the new queries get transformed correctly. Would it be ok if I go with option 1), for now, but create a new JIRA for the change to ODBCMetadataGenerator ? I might even try to fix it myself at some point, but right now I would like to limit the scope of this patch if at all possible. > 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 > > 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
