[
https://issues.apache.org/jira/browse/PHOENIX-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137008#comment-14137008
]
Hudson commented on PHOENIX-1253:
---------------------------------
SUCCESS: Integrated in Phoenix | 4.0 | Hadoop2 #133 (See
[https://builds.apache.org/job/Phoenix-4.0-hadoop2/133/])
PHOENIX-1253 Throw SQLException on prepared stmt (gabrielr: rev
e174793e915de85e4784a6162898e3a5cc06ac10)
*
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixPreparedStatement.java
*
phoenix-core/src/test/java/org/apache/phoenix/jdbc/PhoenixPreparedStatementTest.java
> 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
> Fix For: 5.0.0, 4.2, 3.2
>
> 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)
