[ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12371984 ]
Knut Anders Hatlen commented on DERBY-970: ------------------------------------------ Thanks Dyre, but I have promised that I won't commit the patch yet. To your question about checkJdbcVersionX(): I think all new JDBC 4 metadata calls that require support by the server should call checkJdbcVersionX(). I don't see any value in calling it for methods that return constants (like autoCommitFailureClosesAllResultSets()) or empty result sets (like getClientInfoProperties()). I think getFunctions() and getFunctionParameters(), which I have seen you working on, should call this method. > Add new metadata methods to network client driver > ------------------------------------------------- > > Key: DERBY-970 > URL: http://issues.apache.org/jira/browse/DERBY-970 > Project: Derby > Type: Sub-task > Components: JDBC > Reporter: David Van Couvering > Assignee: Knut Anders Hatlen > Fix For: 10.2.0.0 > Attachments: derby-970-part1-v1.diff, derby-970-part1-v1.stat, > derby-970-part2-v1.diff, derby-970-part2-v1.stat, derby-970-part3-v1.diff, > derby-970-part3-v1.stat > > Implement new JDBC 4.0 DatabaseMetaData methods in the client driver: > - supportsStoredFunctionsUsingCallSyntax() > - autoCommitFailureClosesAllResultSets() > - getClientInfoProperties() > - providesQueryObjectGenerator() > - getSchemas() > - getRowIdLifetime() -- 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
