wiki.techinc.nl/tests/phpunit/includes/page/WikiPageMcrWriteBothDbTest.php

<?php
use MediaWiki\Tests\Revision\McrWriteBothSchemaOverride;

/**
 * Tests WikiPage against the intermediate MCR DB schema for use during schema migration.
 *
 * @covers WikiPage
 *
 * @group WikiPage
 * @group Storage
 * @group ContentHandler
 * @group Database
 * @group medium
 */
class WikiPageMcrWriteBothDbTest extends WikiPageDbTestBase {

	use McrWriteBothSchemaOverride;

	protected function getContentHandlerUseDB() {
		return true;
	}

}
[MCR] RevisionStore, enable insertions for new schema Enable inserts to the new MCR db schema in single slot mode only. TODO: - RELEASE NOTES Notes: - When in MIGRATION_WRITE_NEW or greater, deleting and then restoring a page will result in different data in the revision table. For example, if you delete a page that has text_ids present in the revision table and restore it, the text_ids will be blank after. - When in MIGRATION_WRITE_BOTH or greater the archive table will start to ar_content_model entries where previously it would have been given NULL. This is due to the old content schema having NULL in the db when the default content model is used, but the new schema will always have a value, taken from the content_models table Note: If259b1e1c49ce was squashed into this change. Bug: T183488 Bug: T174024 Change-Id: Ic2221da30c8f6ac2ba42720fcd568f2d0ed70534 2018-01-29 15:54:02 +00:00			`<?php`
Re-namespace RevisionStore and RevisionRecord classes During development a lot of classes were placed in MediaWiki\Storage\. The precedent set would mean that every class relating to something stored in a database table, plus all related value classes and such, would go into that namespace. Let's put them into MediaWiki\Revision\ instead. Then future classes related to the 'page' table can go into MediaWiki\Page\, future classes related to the 'user' table can go into MediaWiki\User\, and so on. Note I didn't move DerivedPageDataUpdater, PageUpdateException, PageUpdater, or RevisionSlotsUpdate in this patch. If these are kept long-term, they probably belong in MediaWiki\Page\ or MediaWiki\Edit\ instead. Bug: T204158 Change-Id: I16bea8927566a3c73c07e4f4afb3537e05aa04a5 2018-09-20 17:29:04 +00:00			`use MediaWiki\Tests\Revision\McrWriteBothSchemaOverride;`
[MCR] RevisionStore, enable insertions for new schema Enable inserts to the new MCR db schema in single slot mode only. TODO: - RELEASE NOTES Notes: - When in MIGRATION_WRITE_NEW or greater, deleting and then restoring a page will result in different data in the revision table. For example, if you delete a page that has text_ids present in the revision table and restore it, the text_ids will be blank after. - When in MIGRATION_WRITE_BOTH or greater the archive table will start to ar_content_model entries where previously it would have been given NULL. This is due to the old content schema having NULL in the db when the default content model is used, but the new schema will always have a value, taken from the content_models table Note: If259b1e1c49ce was squashed into this change. Bug: T183488 Bug: T174024 Change-Id: Ic2221da30c8f6ac2ba42720fcd568f2d0ed70534 2018-01-29 15:54:02 +00:00
			`/**`
			`* Tests WikiPage against the intermediate MCR DB schema for use during schema migration.`
			`*`
			`* @covers WikiPage`
			`*`
			`* @group WikiPage`
			`* @group Storage`
			`* @group ContentHandler`
			`* @group Database`
			`* @group medium`
			`*/`
			`class WikiPageMcrWriteBothDbTest extends WikiPageDbTestBase {`

			`use McrWriteBothSchemaOverride;`

			`protected function getContentHandlerUseDB() {`
			`return true;`
			`}`

			`}`