[ http://issues.apache.org/jira/browse/DERBY-925?page=comments#action_12368709 ]
Dyre Tjeldvoll commented on DERBY-925: -------------------------------------- I agree, no separate JDBC4 implementation should be necessary. But I was thinking that we could have multiple queries in metadata.properties, one that returns the old result set and another that returns the new one with more columns. That way EmbedDatabaseMetaData40 could use the new query, while the existing implementation could use the old query... maybe this would let us keep most of the master files as they are? > 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
