thanks again for the reply. Comments in line.
On Sun, May 31, 2009 at 8:05 PM, Roan Kattouw
<roan.kattouw@gmail.com> wrote:
> On the other hand it seem
> strange though that I can't get easily get all 'events' between two dates.
You can, with recentchanges. It has its limitations, but IMO you
should be able to cope with them.
While looking at this I noticed that log entries for moved pages don't contain revids:
'logaction' => 'move',
'move' => {
'new_ns' => 0,
'new_title' => 'Sandpit/test2'
},
'logtype' => 'move',
'revid' => 0,
'timestamp' => '2009-05-31T21:47:11Z',
'old_revid' => 0,
This seems to be inconsistent: For edits, there's an old_revid and a revid (which are recorded in the log), and when moving a page, it's there's also an old_revid and a revid. However, those are not recorded in the log.
Any ideas as to why that is, and if it doesn't make sense, which bug tracker should it go on?
> Would it somehow be possible to build an intermediate solution? E.g. would
> it be feasible to build a dedicated
> action=query&prop=allchanges&start=...&end=...
> that just solved that problem?
For revisions, possibly. It wouldn't include log events, though.
To be able to query:
(a) all pages that changed between two dates (with the latest revision of that page) and
(b) all revisions that were made between two dates
would be useful, with similar options to prop=revisions and in particular rvprop (and going across all namespaces).
Merging this with log information would not be essential, as most things would be visible from the revisions themselves. Only the deletion log would have to be taken into account, but this could be done in a second query.
Would that be feasible? Something like that would make a mirroring process very easy, as you could just feed in the date of your last update, and get the pages back that you need.
All the best,
Bjoern