db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-319) Derby returns incorrect values for "LENGTH" column of DatabaseMetaData.getProcedureColumns() result set.
Date Sat, 04 Jun 2005 17:58:40 GMT
     [ http://issues.apache.org/jira/browse/DERBY-319?page=all ]

A B updated DERBY-319:

    Attachment: derby-319.stat

Attaching a patch for this issue.  Adds a method to the TypeDesriptor interface to retrieve
the max width of a column based on the ODBC specification found here:


The new method is then used for Derby's implementation of the DatabaseMetaData methods, when
appropriate (esp. in getProcedureColumns()). 

This patch also adds more datatypes to metadata_test.java  for "getColumns()" to ensure that
the new "length in bytes" values are correct for the various types.

> Derby returns incorrect values for "LENGTH" column of DatabaseMetaData.getProcedureColumns()
result set.
> --------------------------------------------------------------------------------------------------------
>          Key: DERBY-319
>          URL: http://issues.apache.org/jira/browse/DERBY-319
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Versions:,,,
>     Reporter: A B
>     Assignee: A B
>     Priority: Minor
>      Fix For:
>  Attachments: derby-319.patch, derby-319.stat
> Based on discussion from the following thread:
> http://article.gmane.org/gmane.comp.apache.db.derby.devel/2585
> The Derby implementation of DatabaseMetaData.getProcedureColumns() returns incorrect
values for the "LENGTH" column of the result, primarily because there is no clear definition
in the JDBC spec regarding what this method is _supposed_ to return.  Discussion in the above-posted
thread concluded that the intent of the JDBC metadata is to "match the ODBC metadata", at
least regard to this particular issue.  So changes reflecting this conclusion should be submitted
to Derby.

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