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

A B commented on DERBY-924:

> That is probably true, but ODBC 2.0 SQLProcedures specifies, that this column should
be VARCHAR(254). 

Can you give a link reference that says this?  I don't deny it, I'm just curious where this
is.  When I look here:


I see the type of REMARKS as "VARCHAR" with no length specification.  It's possible that "254"
is hidden somewhere in there, but if you can give a direct reference that'd be nice :)  My
work with ODBC metadata in the past (esp. DERBY-107) has suggested that while type is important
(ex. CHAR vs VARCHAR, INT vs SMALLINT, nullable vs. not nullable, etc), the specific length
of the VARCHAR hasn't been a concern.  But of course that's just based on observation from
the tests/scenarios I was working with.  If length _is_ specified as part of the ODBC specification,
then perhaps that's something that needs further investigation (as part of a different Jira

> 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