commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Brücke (JIRA) <>
Subject [jira] [Commented] (DBUTILS-117) Error in control the use of ParameterMetaData
Date Thu, 17 Jul 2014 09:28:04 GMT


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:
>             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

View raw message