db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2024) Remove JUnit utility method JDBC.vmSupportsJDBC2
Date Sat, 14 Nov 2009 16:18:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777957#action_12777957
] 

Bryan Pendleton commented on DERBY-2024:
----------------------------------------

I had a quick look at the 15 remaining calls to vmSupportsJDBC2, and they seemed to be:
- test code that needed to know if DriverManager was supported
- test code that needed to know if BigDecimal was supported
- test code that needed to know if [get,set]UnicodeStream was supported

I believe that all these calls can simply be replaced by calling vmSupportsJDBC3,
and then vmSupportsJDBC2 can be removed.

> Remove JUnit utility method JDBC.vmSupportsJDBC2
> ------------------------------------------------
>
>                 Key: DERBY-2024
>                 URL: https://issues.apache.org/jira/browse/DERBY-2024
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Daniel John Debrunner
>
> Replace its use with vmSupportsJDBC3() when required or modify the checks to work upon
the assumption that JDBC3/JSR169 is the base level (e..g holdability is always supported).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message