[
https://issues.apache.org/jira/browse/PHOENIX-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid updated PHOENIX-1253:
----------------------------------
Attachment: PHOENIX-1253b.patch
Thanks for taking a look [~jamestaylor]. Here's the updated patch with your
suggestion (turns out SQLExceptionCode.PARAM_INDEX_OUT_OF_BOUND already existed
in the enum).
I'll get this committed shortly.
> Invalid PreparedStatement.setXXX call should throw SQLException
> ---------------------------------------------------------------
>
> Key: PHOENIX-1253
> URL: https://issues.apache.org/jira/browse/PHOENIX-1253
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.1, 4.1
> Reporter: Gabriel Reid
> Assignee: Gabriel Reid
> Attachments: PHOENIX-1253.patch, PHOENIX-1253b.patch
>
>
> Calling PreparedStatement.setString (or any setXXX method) with an invalid
> parameter index (less then 1 or greater than the number of bind parameters)
> currently throws an IndexOutOfBoundsException based on the underlying List
> used to collect parameters.
> According to the [JDBC API
> docs|http://docs.oracle.com/javase/6/docs/api/java/sql/PreparedStatement.html#setString(int,
> java.lang.String)], this situation should result in a SQLException being
> thrown. This ticket is to change the behavior in Phoenix to be in line with
> the JDBC API docs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
