- 🇳🇿New Zealand quietone
This was fixed in a later issue, #3261629: Database dumps are no longer driver-agnostic → .
Closing as a duplicate.
All migration tests using the Drupal 7 database fixture are are failing on PostgreSQL and SQLite. This was discovered in #3199578-19: Fix EntityReferenceTranslationDeriver process pipeline → when I used the script to generate the dump file.
It fails because of the extra lines added to the database dump file in The db dump command was changed in #838992: Change the uid field from integer to serial by leveraging NO_AUTO_VALUE_ON_ZERO on MySQL → Introduced changes to the \Drupal\Core\Command\DbDumpCommand which adds code to the exported database file.
Here are the lines, removing these and the tests pass with PostgreSQL and SQLite.
// Ensure any tables with a serial column with a value of 0 are created as
// expected.
$sql_mode = $connection->query("SELECT @@sql_mode;")->fetchField();
$connection->query("SET sql_mode = '$sql_mode,NO_AUTO_VALUE_ON_ZERO'");and
// Reset the SQL mode.
$connection->query("SET sql_mode = '$sql_mode'");Generate a new dump
php core/scripts/db-tools.php export --database=legacy > core/modules/migrate_drupal/tests/
fixtures/drupal7.php Then, using PostgreSQL or SQLlite for testing, run any migration test that needs to install the database fixture. One such test would be Drupal\Tests\system\Kernel\Migrate\d7\MigrateSystemConfigurationTest.
Write a patch
review
commit
Closed: duplicate
10.1 ✨
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This was fixed in a later issue, #3261629: Database dumps are no longer driver-agnostic → .
Closing as a duplicate.