[
https://issues.apache.org/jira/browse/DBUTILS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076153#comment-14076153
]
Christoph Brücke commented on DBUTILS-117:
------------------------------------------
Thanks for the nice words. Too bad it won't make it into 1.6, but I can live
with SNAPSHOT.
The problem with unit tests is, that the reported defect is highly driver
dependent. Naturally I have a unit test, but I could only reproduce it with
Oracle 12c, thus it needs a real connection. Is there already some way to mock
a connection? Should I create a new {{AbstractQueryRunnerTest}} class along
with {{MockPreparedStatement}} that produces an {{SQLException}} on
{{getParameterMetaData()}}?
I'd be more than happy to provide everything that is needed to properly fix
this issue but I might need some advice on how to proceed from here.
> Error in control the use of ParameterMetaData
> ---------------------------------------------
>
> Key: DBUTILS-117
> URL: https://issues.apache.org/jira/browse/DBUTILS-117
> Project: Commons DbUtils
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Vadim Smirnov
> Priority: Minor
> Labels: easyfix, newbie
> Fix For: 1.7
>
> Attachments: DBUTILS-117.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Error in fillStatement method of AbstractQueryRunner class.
> There is no try...catch statement near pmd = stmt.getParameterMetaData();
> So method fails instead of automaticallye turning pmdKnownBroken to true.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
