[teiid-issues] [JBoss JIRA] (TEIID-2098) Caching does not interact well with Statement.setMaxRows
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Thu Jul 12 14:26:12 EDT 2012
[ https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins updated TEIID-2098:
----------------------------------
It will need to be a KI that Statement.setMaxRows does not affect callablestatements that return out/inout/return parameters.
> Caching does not interact well with Statement.setMaxRows
> --------------------------------------------------------
>
> Key: TEIID-2098
> URL: https://issues.jboss.org/browse/TEIID-2098
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.1
>
>
> Most of the time setting maxRows will cause the plan to not be cachable and the results will be cached/reused regardless of what subsequent maxRows are set to.
> Finally a general issue is that if the query cannot have maxRows set as a limit (if there is already a limit or it's a procedure call) then the maxRows is ignored.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list