[teiid-issues] [JBoss JIRA] (TEIID-2101) Statement.setMaxRows is not always used
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Thu Aug 8 12:57:26 EDT 2013
[ https://issues.jboss.org/browse/TEIID-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795877#comment-12795877 ]
Steven Hawkins commented on TEIID-2101:
---------------------------------------
This also addressed a narrow issue - using the cache directive on a callable statement that returns parameters and has the max rows set will be cached as if it were the full result. Subsequent access of the cached results with a larger row limit will not see the missing rows.
> 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
More information about the teiid-issues
mailing list