Last modified: 2008-08-02 06:16:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T17011, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 15011 - $wgAPIMaxDBRows doesn't seem used
$wgAPIMaxDBRows doesn't seem used
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-08-02 04:24 UTC by Chad H.
Modified: 2008-08-02 06:16 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Chad H. 2008-08-02 04:24:39 UTC 
As of trunk (r38413), the limit $wgAPIMaxDBRows doesn't seem used. It's used once within ApiQueryBase::checkRowCount(), but that method doesn't seem to be called from anywhere, rendering it useless. If this setting has been obsoleted by other methods, then it should probably be marked as such. Thanks.
Comment 1 OverlordQ 2008-08-02 04:36:24 UTC 
re bug 13511 it was added in case something needed to make a row check, but I guess there hasn't been anything needing it since it was added in r32466
Comment 2 Chad H. 2008-08-02 06:16:39 UTC 
I see, I didn't notice that :-) Closing.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links