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-1094) Make DatabaseMetaData.getProcedureColumns() JDBC4 compliant
Date Mon, 13 Mar 2006 15:31:41 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1094?page=all ]

Dyre Tjeldvoll updated DERBY-1094:
----------------------------------

    Attachment: derby-1094.preliminary.diff

I'm attaching a preliminary patch for the GetProcedureColumn.java and TypeId.java part of
this issue. The patch cannot be completed until consensus is reached on how to modify/update
metadata.properties, where the queries are stored. It would be nice if I could get some feedback
on this first part, while I'm waiting. Thanks.

> Make DatabaseMetaData.getProcedureColumns() JDBC4 compliant
> -----------------------------------------------------------
>
>          Key: DERBY-1094
>          URL: http://issues.apache.org/jira/browse/DERBY-1094
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC
>     Versions: 10.2.0.0
>     Reporter: Dyre Tjeldvoll
>     Assignee: Dyre Tjeldvoll
>      Fix For: 10.2.0.0
>  Attachments: derby-1094.preliminary.diff
>
> The result set returned by getProcedureColumns() must be extended with 7 additional columns
in JDBC 4.0; COLUMN_DEF, SQL_DATA_TYPE, SQL_DATETIME_SUB, CHAR_OCTET_LENGTH, ORDINAL_POSITION,
IS_NULLABLE and SPECIFIC_NAME. The returned result set should be ordered by PROCEDURE_SCHEMA,
PROCEDURE_NAME and SPECIFIC_NAME

-- 
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