[ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12369672 ]
Kathey Marsden commented on DERBY-970: -------------------------------------- Sorry I didn't look at this earlier I have a few questions as I try to come up to speed on the issues. 1) Could you clarify the issue with JDK 1.6? >From what I understand, the issue is: We just don't have access to the JDK 1.6 interfaces because in our build we don't build with JDK 1.6. Is that correct? If that is the case, can our SystemProcedure just call our internal implementation? 2) With your plan will metadata.properties remain as is and we keep the stored prepared statements? 3)Could you epxplain how thie factory solution would work a little more? And a couple of tangental questions: 4) Do you understand how metadata.properties changes are handled with regard to soft upgrade, downgrade, upgrade, etc currentlyy? I have had on my list for a long time to research what is happenning in Derby with this as it was the source of intractable upgrade issues in the past and the mechanism that I knew of to handle it (dropping the SPS's whenever the version changed) is no longer in Derby. I just haven't been able to get to researching it yet. 5) Is there a general problem with incompatiblity of compiled Stored Prepared Statements in databases that may have been created with different JVM versions? On the earlier suggestions: Either c or d would be a fatal blow to client/server compatibility, so they have all the appeal of euthanasia for client/server compat. > 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
