993baa3493
When this was originally written, the plan was to read both the old and new fields during the transition period, while stopping writes to them midway through. It turns out that the WHERE conditions to do read-both correctly are generally not handled well by the database and working around that would require a lot of complicated code (see what's being removed from ApiQueryUserContribs here, for example). We can simplify things greatly by instead having it write both fields during the transition period, reading from the old for the first part and the new for the second part, as is being done for MCR. Bug: T204669 Change-Id: I4764c1c7883dc1003cb12729455c8107319f70b1 Depends-On: I845f6ae462f2539ebd35cbb5f2ca8b5714e2c1fb Depends-On: I88b31b977543fdbdf69f8c1158e77e448df94e11 |
||
|---|---|---|
| .. | ||
| ApiQueryBasicTest.php | ||
| ApiQueryContinue2Test.php | ||
| ApiQueryContinueTest.php | ||
| ApiQueryContinueTestBase.php | ||
| ApiQueryRevisionsTest.php | ||
| ApiQueryTest.php | ||
| ApiQueryTestBase.php | ||
| ApiQueryUserContribsTest.php | ||