[
https://issues.apache.org/jira/browse/DBUTILS-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246805#comment-14246805
]
Sebb commented on DBUTILS-117:
------------------------------
However, the original issue (as per the description) remains.
The initial call to getParameterMetaData() needs to allow for catching at least
SQLFeatureNotSupportedException, possibly other types of SQLE as well.
The example quoted in the description was SQLSyntaxErrorException (which seems
a bit odd).
Should the code catch every SQLEx ? Ideally not, as that might mask genuine
errors.
> Error handling possible getParameterMetaData() results
> ------------------------------------------------------
>
> 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-tests.patch, 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.3.4#6332)
