Closed (fixed)
Project:
MemSQL
Version:
8.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Feb 2020 at 15:38 UTC
Updated:
30 Jun 2020 at 11:14 UTC
Jump to comment: Most recent
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
Comment #3
sinn commented