[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ]
Dyre Tjeldvoll updated DERBY-1093:
----------------------------------
Attachment: derby-1093.v1.diff
derby-1093.v1.stat
derbyall_report.txt
I have attached a patch (derby-1006.v1.*) for this. There is currently much
discussion around metadata and upgrade, so a couple of comments are in order:
1) As mentioned previously, the patch introduces a NEW query (getProcedures40)
to ensure that it gets picked up, even when doing soft upgrade
2) I have tried to run the phaseTester.java test, but since I have modified the
metadata.java master files, the output is expected to change (as I understand
it). The resulting output was attached previously (upgrade.txt)
3) A new column is added to the returned result set, but the value for this
column comes from an existing column in a system table, so this should not be
an upgrade problem (?)
4) If/when this patch gets accepted into the code line, I will log a new JIRA
for the task of modifying ODBCMetaDataGenerator to transform the new queries
into ODBC queries, so that the old queries can be removed from
metadata.properties.
> 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
