[teiid-issues] [JBoss JIRA] Resolved: (TEIID-98) Prepared/CallableStatement parameter indexes are not correct.
[
https://issues.jboss.org/browse/TEIID-98?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins resolved TEIID-98.
---------------------------------
Fix Version/s: (was: 9.x)
Resolution: Partially Completed
retrieval indexes have been corrected based upon prior changes. Only the setXXX indexes
are not strictly enforced. We could add client side validation that takes into account
out parameter information to ensure consecutive indexes starting at 1. That may break
older client code that for whatever reason is not registering out parameters. It seems
best to just mark as resolved and reopen if it becomes an issue for a user.
Prepared/CallableStatement parameter indexes are not correct.
-------------------------------------------------------------
Key: TEIID-98
URL: https://issues.jboss.org/browse/TEIID-98
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.x
Reporter: Steven Hawkins
Priority: Minor
Original Estimate: 2 days
Remaining Estimate: 2 days
All parameter indexes are treated as relative rather than absolute. We should not accept
values less than 1 and should ensure that the values specified are continuous.
Also, return parameters should be considered index 1 regardless of where they are in the
procedure metadata. For example in defer_testDefect24952 in TestMMStoredProcedure ?=call
sp.sp_count_rows_between(?, ?) should have a return value at index 1 from the driver
perspective, but instead it has index 3.
see also defect 24952
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira