You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/09/16 12:33:33 UTC
[jira] [Created] (PHOENIX-1253) Invalid PreparedStatement.setXXX
call should throw SQLException
Gabriel Reid created PHOENIX-1253:
-------------------------------------
Summary: 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
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)