[
http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_12377221 ]
Rick Hillegas commented on DERBY-1180:
--------------------------------------
Committed 4c at subversion revision 398594. Derbyall ran cleanly with 4a before
the MessageId migration and I did not rerun it against 4c. I did rerun the
jdbc4 tests against 4c and they passed.
Unfortunately, this patch introduces another instance of the following build
warning which has been discussed on derby-dev. I believe that Knut Anders has a
plan for fixing these:
[javac]
/home/rh161140/derby/mainline/trunk/java/client/org/apache/derby/client/am/LogicalConnection40.java:43:
warn
ing: getTypeMap() in org.apache.derby.client.am.LogicalConnection implements
getTypeMap() in java.sql.Connection; return
type requires unchecked conversion
[javac] found : java.util.Map
[javac] required: java.util.Map<java.lang.String,java.lang.Class<?>>
[javac] public class LogicalConnection40
> Add vacuous implementations of missing JDBC4 methods
> ----------------------------------------------------
>
> Key: DERBY-1180
> URL: http://issues.apache.org/jira/browse/DERBY-1180
> Project: Derby
> Type: New Feature
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: Rick Hillegas
> Assignee: Kristian Waagan
> Attachments: bug1180_1.diff, bug1180_embeddedStarter.diff,
> derby-1180-1a-embedded.diff, derby-1180-1a-embedded.stat,
> derby-1180-2a-client.diff, derby-1180-2a-client.stat,
> derby-1180-3a-testing.diff, derby-1180-3a-testing.stat,
> derby-1180-4a-logcialconnection_and_tests.diff,
> derby-1180-4a-logcialconnection_and_tests.stat,
> derby-1180-4b-logicalconnection_and_tests.diff,
> derby-1180-4c-logicalconnection_and_tests.diff
>
> If you run the VerifySignatures test, you will see a lot of JDBC4 methods
> which don't appear in our implementation yet. We need to add vacuous
> implementations for these methods which raise
> SQLFeatureNotSupportedExceptions. Most of these methods won't need any more
> attention because they refer to features (like xml and national strings)
> which we don't support. We will open additional JIRAs for the methods which
> need non-vacuous implementations.
--
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
