Seed database not importing successfully

[grantfitzsimmons]

While setting up locally with the sp7demofish seed database, I ran into the seed import failing with "No database selected." Root cause: docker-compose.yml's mariadb service doesn't set MYSQL_DATABASE, which the official image needs to auto-create the database before running the seed script — needed once the dump's CREATE DATABASE/USE lines are stripped per your seed-database README. Adding that one env var line fixed it locally.

[grantfitzsimmons]

Suggested by Jainish Shah:

Root cause is exactly one conditional in the official image's (MARIADB) own entrypoint script (docker-entrypoint.sh, docker_exec_client()):

docker_exec_client() {
if [ -n "$MYSQL_DATABASE" ]; then
set -- --database="$MYSQL_DATABASE" "$@"
fi
mariadb --protocol=socket -uroot -hlocalhost --socket="${SOCKET}" "$@"
}

Every .sql file in /docker-entrypoint-initdb.d/ gets piped through this function via docker_process_sql. It only passes --database= to the client if MYSQL_DATABASE is set — docker-compose.yml's mariadb service doesn't set it. So the client session for the seed import has no default database selected at all. Combine that with seed-database/README.md's own requirement to strip CREATE DATABASE/USE from any dump, fails immediately with ERROR 1046 (3D000): No database selected.

Fix: add MYSQL_DATABASE=${DATABASE_NAME} to the mariadb service's environment block in docker-compose.yml. One line, no other side effects — confirmed working locally with the sp7demofish seed dump after stripping its CREATE DATABASE/USE lines per the README.