[ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12369894 ]
David Van Couvering commented on DERBY-970: ------------------------------------------- I'll weigh in on a couple of things: - A lot of the complexity in your solution seems to be dependent on the fact that we can't require JDK 1.6 to build Derby. I think that requirement needs to continue to exist until JDK 1.6 goes GA, but are we as a community willing to commit to using JDK 1.6 (assuming we can find a build approach that works) once it's GA, so we don't have these kinds of issues come up over and over? - I think it makes sense to give new revisions of old metadata stored procs new names - I think it makes a lot of sense to move the new metadata calls into the old metadata class so you don' t have to pick your class at runtime through reflection - I also agree I don't see the obvious value making metadata calls stored procedures rather than just prepared statements. David > 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 > Reporter: David Van Couvering > Assignee: Knut Anders Hatlen > > Implement new JDBC 4.0 DatabaseMetaData methods in the client driver: > - supportsStoredFunctionsUsingCallSyntax() > - autoCommitFailureClosesAllResultSets() > - getClientInfoProperties() > - providesQueryObjectGenerator() > - getSchemas() -- 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
