Hi!
From looking at DB scheme I cannot find an efficient
way of getting the
list of null revisions or opposite (no null revisions list).
With LIMIT
paging (for custom API). When I GROUP then ORDER and LIMIT, it behaves
extremly slow.
It seems that I should use very inefficient GROUP BY rev_text_id (and
also MySQL not offering FIRST / LAST aggregate functions) and also there
is no index on rev_text_id by default :-( I wish there was a field like
rev_minor_edit but for detection of null revisions, such as these
generated by XML import / export. They confuse the logic of my wiki
synchronization script. However, even if I were able to persuade to
include these features into the scheme, 1.15 which customers use, was
already released some time ago, anyway :-( So probably the core patch is
the only efficient way to solve my problem?
Dmitriy