[
https://issues.jboss.org/browse/TEIID-2101?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2101.
-----------------------------------
Fix Version/s: 8.5
Resolution: Done
Addressed with both server side and client side logic. Procedures return parameters and
cached results are appropriately handled.
We may however be enforcing the max rows too broadly on the server as it limits result
caching. This will need to be refined (possibly with something like the readAll
cachedirective being exposed through hinting).
Statement.setMaxRows is not always used
---------------------------------------
Key: TEIID-2101
URL:
https://issues.jboss.org/browse/TEIID-2101
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver, Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.5
The maxRows setting is not used when returning cached result sets or when getting a
result set from a callablestatement procedure that returns parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira