[ 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: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlprocedurecolumns.asp 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 issue). > 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: 10.2.0.0 > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
