Hi,
Currently the doc says
--- $cfg['MaxRows'] integer Number of rows displayed when browsing a result set. If the result set contains more rows, "Previous" and "Next" links will be shown. ---
Due to [0] I suggest this:
--- $cfg['MaxRows'] integer Number of rows displayed when browsing a result set and no LIMIT clause is used. If the result set contains more rows, "Previous" and "Next" links will be shown. ---
I believe that an explicit LIMIT in the query has priority over MaxRows; this is the current behavior.
[0] https://sourceforge.net/tracker/index.php?func=detail&aid=3354433&gr...
2012/1/27 Marc Delisle marc@infomarc.info:
Hi,
Currently the doc says
$cfg['MaxRows'] integer Number of rows displayed when browsing a result set. If the result set contains more rows, "Previous" and "Next" links will be shown.
Due to [0] I suggest this:
$cfg['MaxRows'] integer Number of rows displayed when browsing a result set and no LIMIT clause is used. If the result set contains more rows, "Previous" and "Next" links will be shown.
I believe that an explicit LIMIT in the query has priority over MaxRows; this is the current behavior.
If this is how it's currently working, then I agree on the proposed change in the message. The size of LIMIT could be mentioned, but it is probably redundant : if it is smaller than MaxRows, it's the same as not specifying a LIMIT, because the number of rows will be smaller than MaxRows. If it is bigger, LIMIT is specified.
On Fri, Jan 27, 2012 at 3:09 PM, Marc Delisle marc@infomarc.info wrote:
Hi,
Currently the doc says
$cfg['MaxRows'] integer Number of rows displayed when browsing a result set. If the result set contains more rows, "Previous" and "Next" links will be shown.
Due to [0] I suggest this:
$cfg['MaxRows'] integer Number of rows displayed when browsing a result set and no LIMIT clause is used. If the result set contains more rows, "Previous" and "Next" links will be shown.
I believe that an explicit LIMIT in the query has priority over MaxRows; this is the current behavior.
As pointed out by Marc in the tracker, since this behavior has been there
for years I guess many people are using the LIMIT clause in place of the navigation panel. So let's keep it the way it is. And yes, the change of documentation is appropriate.