frommeandClaude Opus 5
2a8649fc6d
Development ran MySQL 8.4 while production runs MariaDB, so nothing engine-specific was ever exercised on the engine it ships on. DATABASE_URL carries serverVersion=mariadb-* now, which is what makes DBAL pick its MariaDB platform. This matters most for the test environment: it reads DATABASE_URL from the committed .env and not from .env.dev.local, so a MySQL version there had the suite running on MySQL84Platform against a MariaDB server - and schema:validate reporting every nullable and every json column as drift. With the platform right, a db_test built from the mapping is in sync. The post-start hooks create db_test and grant the db user, which ddev does not do on its own, and sync the schema from the entity mapping. Without them the first test run after a fresh start fails on the missing database. The remaining changes in config.yaml are ddev's own regeneration of the commented reference section. Co-Authored-By: Claude Opus 5 <[email protected]>