Drupal\KernelTests\Core\Database\InvalidDataTest::testInsertDuplicateData
Insert succeeded when it should not have.

/core/tests/Drupal/KernelTests/Core/Database/InvalidDataTest.php:39

2) Drupal\KernelTests\Core\Database\InvalidDataTest::testInsertDuplicateDataFromSelect
Insert succeeded when it should not have.

/core/tests/Drupal/KernelTests/Core/Database/InvalidDataTest.php:116

FAILURES!
Tests: 2, Assertions: 2, Failures: 2.

MemSQL requires that any PRIMARY or UNIQUE index must be identical to or a superset of the shard key. Rows which might have a primary key conflict must map to the same partition in order for uniqueness to be enforced. (https://docs.memsql.com/v6.8/concepts/distributed-sql).

Can be fixed in Drupal\Driver\Database\memsql\Schema.

Comments

sinn created an issue. See original summary.

  • sinn committed 1c5ab7e on 8.x-1.x
    Issue #3112822: InvalidDataTest is failed. Added shard_id field.
    
sinn’s picture

Version: » 8.x-1.0-alpha1
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.