db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant
Date Fri, 17 Mar 2006 17:34:32 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12370849 ] 

Kathey Marsden commented on DERBY-1093:
---------------------------------------

Please wait to commit  this patch until the current issues with ugprade and metadata have
been identified and there is community concensus on how to approach for 10.2.  This change
affects  metadata.java which impacts the upgrade tests and makes the  current task of identifying
the issues that exist even more difficult.  Relevant issues are: DERBY-1076,  DERBY-1107,
DERBY-1120, DERBY-1075.




> 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


Mime
View raw message