https://bugzilla.wikimedia.org/show_bug.cgi?id=17993

Bergi <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #10 from Bergi <[email protected]> 2011-06-14 16:19:09 UTC ---
Isn't there even an SQL command to return just the length of the matched set
instead of the items themselves? Of course Roans explanation is good, but this
is only the price for one query. If my aim was to count the set, I would have
to make all the continue-queries, which means the same searching through the
table as it would have been for one query. Of course, this might be an argument
to repeal any api limits, but the real advantage is the save of bandwidth and
PHP-requests.

A script that could profit from this would be
http://de.wikipedia.org/wiki/MediaWiki:Gadget-revisionCounter.js. Here just two
queries would have to be done: 
* api.php?action=query&prop=revisions&titles=Foo&countonly
* api.php?action=query&prop=revisions&titles=Foo&rvuser=Bar&countonly
Another example would be a tool to retrieve the number of template
transclusions, just like http://toolserver.org/~jarry/templatecount/. There a
simple call to
api.php?action=query&list=embeddedin&eititle=Template:Foo&countonly would be
enough.

The countonly parameter should work for all properties but "info",
"categoryinfo" and "pageprops", and for all lists but "random". The "search"
list already provides a "totalhits" parameter, which might be interesting. I
don't think counting would be useful for meta queries.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to