phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1253) Invalid PreparedStatement.setXXX call should throw SQLException
Date Wed, 17 Sep 2014 07:50:33 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136905#comment-14136905
] 

Hudson commented on PHOENIX-1253:
---------------------------------

SUCCESS: Integrated in Phoenix | 3.0 | Hadoop1 #213 (See [https://builds.apache.org/job/Phoenix-3.0-hadoop1/213/])
PHOENIX-1253 Throw SQLException on prepared stmt (gabrielr: rev 963ea0f9140244dc969da627f191d882cf2fd2f2)
* phoenix-core/src/test/java/org/apache/phoenix/jdbc/PhoenixPreparedStatementTest.java
* phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixPreparedStatement.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
>         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)

Mime
View raw message