[
https://issues.apache.org/jira/browse/DBUTILS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466606#comment-13466606
]
William R. Speirs commented on DBUTILS-101:
-------------------------------------------
What is the exception? If it's simply an SQLException, then how can DBUtils
distinguish between a where clause that is invalid and one where the
pmdKnownBroken might just need adjusting?
> QueryRunner fails to detect broken pmd
> --------------------------------------
>
> Key: DBUTILS-101
> URL: https://issues.apache.org/jira/browse/DBUTILS-101
> Project: Commons DbUtils
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Sébastien Le Ray
> Priority: Minor
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> I recently fall across a strange issue with SQLServer JDBC driver and
> DBUtils. PreparedStatement#getParameterMetadata sometimes throw an
> SQLException which is not caught in fillParameter.
> The issue arises with pagination queries like
> SELECT * FROM ( SELECT ROW_NUMBER() OVER ( ORDER BY field1 ASC) AS RowNum,
> field1 as id, field2 as reference FROM MY_TABLE WHERE 1 = 1 AND field1 LIKE
> ?) as toPaginate WHERE RowNum >= 1 AND RowNum <= 50
> the query is fine but getParameterMetaData throw an exception complaining
> about a syntax error near WHERE. Passing pmdKnownBroken to true solves this
> but stmt.getParameterMetaData(); should be wrapped to catch the exception to
> adjust pmdKnownBroken.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
