[
http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12369895 ]
Daniel John Debrunner commented on DERBY-970:
---------------------------------------------
David Van Couvering wrote:
> but are we as a community willing to commit to using JDK 1.6
Not sure what exactly you mean here, require 1.6 to build Derby instead of 1.4?
You have to remember you cannot regress the ability of someone to build Derby
currently,
questions that arise in my mind are:
- when will 1.6 be available on mac os,
- am I forced to use Sun's JDK to build if no others exist, I happily
build & test using IBM's vms today.
- if Sun is the only JDK 1.6 vm out there, are it's licence terms
acceptable to most folks, today since
the build is 1.4 based, folks have choice.
- if someone only cares about 1.4/1.5 today, are we forcing them to
download 1.6?
> 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
