[
https://issues.apache.org/jira/browse/CLOUDSTACK-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708807#comment-13708807
]
ASF subversion and git services commented on CLOUDSTACK-1948:
-------------------------------------------------------------
Commit 9b521be4d0b63659be1b6ef5c306f45faddb9501 in branch refs/heads/master
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9b521be ]
CLOUDSTACK-1948: fixed pagesize to support -1 (unlimited) value
> users can no longer set global limits to -1 (e.g. pagesize)
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-1948
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1948
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Alena Prokharchyk
> Fix For: 4.2.0
>
>
> Just installed 4.1 over a 4.0 install, and ran into an issue where the max
> pagesize global parameter was set to -1, which worked to effectively disable
> paging in 4.0, but 4.1 passes the -1 right on to the SQL query, which mysql
> hates.
> management server log shows "LIMIT 0, -1" in mysql statements. I'm assuming
> that a non-positive integer used to just remove the limit clause, since it
> worked in 4.0
--
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
