[ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12371737 ]
Kathey Marsden commented on DERBY-970: -------------------------------------- Thanks Knut for the clarification. Metadata seems such a delicate area right now and as you say the tests are behind the feature devopment. I get a little wary of all the changes happening in this area, given the testing situation and the outstanding bugs. I think maybe we should hold off on metadata checkins until DERBY-514 is complete and DERBY-1120 and DERBY-1124 are resolved. Also a clear strategy on DERBY-1107 would be good as well, but not required. I know these are not your issues but I think it would be a good cautionary measure to get these core testing issues and bugs resolved with metadata resolved before checkin in more metadata enhancements. Thoughts? > 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
