Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 11 Apr 2013 02:18:14 +0000 (UTC)
From: "Marcus Sorensen (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12640900.1365122574367.147364.1365646694478@arcas>
In-Reply-To: <JIRA.12640900.1365122574367@arcas>
References: <JIRA.12640900.1365122574367@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-1948) users can no longer set global
 limits to -1 (e.g. pagesize)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Sorensen updated CLOUDSTACK-1948:
----------------------------------------

    Issue Type: Bug  (was: Improvement)
    
> 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
>            Reporter: Marcus Sorensen
>             Fix For: 4.1.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