[
https://issues.apache.org/jira/browse/DBUTILS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064741#comment-14064741
]
Christoph Brücke commented on DBUTILS-117:
------------------------------------------
Yes you're right. But it already does that at the near bottom of
{{AbstractQueryRunner#fillStatement(PreparedStatement, Object...)}} where it
tries to get the parameter types.
I don't really see a problem with the proposed approach. Even in the event of a
{{SQLException}} that is legit, i.e. not related to broken
{{ParameterMetaData}}, it will be re-thrown eventually. The real magic happens
in the call to {{stmt.setObject(...)}} and if there is something wrong with the
connection this will cause a proper {{SQLException}}.
> 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
> 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)
