[ http://issues.apache.org/jira/browse/DERBY-925?page=comments#action_12369193 ]
Dyre Tjeldvoll commented on DERBY-925: -------------------------------------- First of all, metadata.properties WILL have to change for JDBC 4.0, and it already has. David has already added new queries for getFunctions and getFunctionParameters (and others I think), but they only return empty resultsets. For DERBY-924 I changed the query for getFunctions to return the correct values, but I have not created a system procedure that invokes this method so that it can be used in client server mode. I guess that means that a JDBC 4.0 client that tries to invoke getFunctions will get a "no such PROCEDURE" error or something, but I have not verified this. I guess this depends on the implementation of DatabaseMetaData in the client? I don't know how the jvm version affects this. Presumably it would still be possible to run an old version of Derby in java 1.6, but then one would get a "no such method" exception when attempting to invoke the new methods? For getProcdures and getProcedureColumns there should not be any upgrade issues, since they already exist in JDBC 3.0. Note however, that metadata.properties will have to change for these as well. A JDBC 4.0 client should be able to execute these methods against a JDBC 3.0 server without any problems as long as it doesn't attempt to access any of the new columns in the returned result set. If it does, I expect that the conventional "no such column" exception will be thrown (can be avoided by using ResultSetMetaData defensively, I think). > Implement new JDBC 4 metadata API getFunctionParameters() > --------------------------------------------------------- > > Key: DERBY-925 > URL: http://issues.apache.org/jira/browse/DERBY-925 > Project: Derby > Type: New Feature > Components: JDBC > Versions: 10.2.0.0 > Environment: JDK 1.6 > Reporter: David Van Couvering > Assignee: Dyre Tjeldvoll > Attachments: TypePrinter.java > > I am currently implementing this to return an empty result set so at least > we're compliant, but we should be able to provide real metadata here. -- 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
