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] Updated: (DERBY-1093) Make DatabaseMetaData.getProcedures() JDBC4 compliant
Date Fri, 21 Apr 2006 09:52:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1093?page=all ]

Dyre Tjeldvoll updated DERBY-1093:

    Attachment: derby-1093.v2.diff

Although there are still two "blocking" issues open, I'm now attaching a new patch, derby-1093.v2
to this issue. In addition to passing derbyall the patch also passes the jdbc4 suite (embedded
and DerbyNetClient), metadata.java and odbc_metadata.java  in all frameworks with java 1.5
and 1.6_b80, and in DerbyNetClient with java 1.3.

Finally, the patch passes the new UpgradeTest was  with both java 1.5 and java 1.6. (The output
is slightly modified since the master for metadata.java was also modified).

Please review.

> 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:
>  Attachments: derby-1093.v1.diff, derby-1093.v1.stat, derby-1093.v2.diff, derby-1093.v2.stat,
derbyall_report.txt, derbyall_report.v2.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
> 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