tonyair/silverstripe-cms
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-cms synced 2024-10-22 08:05:56 +02:00
Code Issues Projects Releases Wiki Activity

FIX InnoDB FULLTEXT compat in tests

Browse Source 
> InnoDB FULLTEXT indexes have special transaction handling characteristics due its caching and batch processing behavior. Specifically, updates and insertions on a FULLTEXT index are processed at transaction commit time, which means that a FULLTEXT search can only see committed data. The following example demonstrates this behavior. The FULLTEXT search only returns a result after the inserted lines are committed.

https://dev.mysql.com/doc/refman/5.6/en/innodb-fulltext-index.html#innodb-fulltext-index-transaction
This commit is contained in:
Ingo Schommer 2020-04-09 10:23:02 +12:00
parent dd839ca2d9
commit e51bd421a6
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tests/php/Search/DatabaseSearchEngineTest.php
View File

@ -13,6 +13,11 @@ class DatabaseSearchEngineTest extends SapphireTest
{ {
protected $usesDatabase = true; protected $usesDatabase = true;
/**
* @var bool InnoDB doesn't update indexes until transactions are committed
*/
protected $usesTransactions = false;
public static function setUpBeforeClass() public static function setUpBeforeClass()
{ {
parent::setUpBeforeClass(); parent::setUpBeforeClass();
@ -46,5 +51,4 @@ class DatabaseSearchEngineTest extends SapphireTest
$results->First()->Title $results->First()->Title
); );
} }
} }

5
tests/php/Search/SearchFormTest.php
View File

@ -44,6 +44,11 @@ class ZZZSearchFormTest extends FunctionalTest
*/ */
protected $mockController; protected $mockController;
/**
* @var bool InnoDB doesn't update indexes until transactions are committed
*/
protected $usesTransactions = false;
public function waitUntilIndexingFinished() public function waitUntilIndexingFinished()
{ {
$schema = DB::get_schema(); $schema = DB::get_schema();