You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2009/11/20 00:43:39 UTC
[jira] Updated: (DERBY-2024) Remove JUnit utility method
JDBC.vmSupportsJDBC2
[ https://issues.apache.org/jira/browse/DERBY-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Pendleton updated DERBY-2024:
-----------------------------------
Attachment: removeFunction.diff
Attached 'removeFunction.diff' is a patch proposal to remove vmSupportsJDBC2()
from the codeline and replace the 15-or-so current calls to that function by calling
vmSupportsJDBC3() instead.
A full regression test run in my environment was clean.
It seems like this patch introduces the most risk in the area of JSR169 testing.
Is there anyone who has a JSR169-based test environment who can perform
a regression test run with this patch, or give it a quick code review, before I commit it?
thanks,
bryan
> 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
> Attachments: removeFunction.diff
>
>
> 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.