Agree, backwards compatibility is important, but it has to be balanced with efforts required to maintain query.php.. Every db schema change must be looked at to see if query.php must be updated. Internal api changes may also impact its functions and performance. IIRC, there are already some queries not working as intended.
At the very least, we can analyze web logs to see which query.php functions are being used, and disable the rest. There was logging functionality built into query.php, and the server should have an alternative log that could be grep-ed. Can a server admin look at that? Thx! On 2/2/08, Tim Starling <[EMAIL PROTECTED]> wrote: > Yuri Astrakhan wrote: > > For those who use old query.php API interface: > > > > Per http://bugzilla.wikimedia.org/show_bug.cgi?id=12881 , query.php has > > been fully ported to the api.php, and thus no longer needed. Unless > > there are significant reasons to keep it around, it will be removed both > > from the extensions and from the mediawiki sites fairly soon. > > > > Isn't backwards compatibility enough of a reason? Surely it's a lot easier > to keep it around than to rewrite everything that uses it. > > -- Tim Starling > > > _______________________________________________ > MediaWiki-l mailing list > [EMAIL PROTECTED] > http://lists.wikimedia.org/mailman/listinfo/mediawiki-l > _______________________________________________ Mediawiki-api mailing list [email protected] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
