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] Commented: (DERBY-924) new JDBC4 metadata API getFunctions() needs to be implemented
Date Tue, 28 Feb 2006 15:31:43 GMT
    [ http://issues.apache.org/jira/browse/DERBY-924?page=comments#action_12368112 ] 

Dyre Tjeldvoll commented on DERBY-924:

Actually, my prvious comment was wrong. getProcedures returns CAST ((JAVACLASSNAME || '.'
|| ALIASINFO->getMethodName()) AS VARCHAR(32672)) AS REMARKS, so I'll use that for getFunctions()
as well.

There is a comment in metadata.properties saying:

# 'REMARKS' column is VARCHAR(32672), which is the max length allowed
# for a VARCHAR.  This is because Java methods with the complete
# package name plus possible signature can grow to be rather long.

That is probably true, but ODBC 2.0 SQLProcedures specifies, that this column should be VARCHAR(254).
But I guess it is better to be consitent with the existing getProcedures() implementation.

> new JDBC4 metadata API getFunctions() needs to be implemented
> -------------------------------------------------------------
>          Key: DERBY-924
>          URL: http://issues.apache.org/jira/browse/DERBY-924
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Versions:
>  Environment: JDK 1.6
>     Reporter: David Van Couvering
>     Assignee: Dyre Tjeldvoll

> For now I am implementing this to return empty result set so at least we're compliant,
but we should be able to implement this one

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