database · inferred from evidence
MySQL
A relational database management system, referenced as the type of Cloud SQL instance.
- MySQL MCP: ER_BAD_DB_ERROR Unknown database (fix MYSQL_DB or create it)
Fixes the MySQL MCP server failing with ER_BAD_DB_ERROR: Unknown database. Auth succeeded but the MYSQL_DB name does not exist on the server. The fix is creating the database or correcting the name. Use when auth works but the database is r
- MySQL MCP: ER_ACCESS_DENIED_ERROR Access denied for user (check MYSQL_USER/PASS)
Fixes the MySQL MCP server failing with ER_ACCESS_DENIED_ERROR: Access denied for user. The cause is wrong credentials in the server env (MYSQL_USER / MYSQL_PASS) or the user lacking rights from the client host. The fix is verifying credent
- Files copied in the Dockerfile are missing at runtime (anonymous volume shadows the image content)
Fixes files 'disappearing' from a container when a VOLUME instruction or -v covers the directory COPY populated. Use when the image build clearly copies files but the running container shows an empty directory. Not for .dockerignore or COPY
- Cloud SQL Proxy: dial tcp :3307 getsockopt connection timed out
Fixes Cloud SQL Proxy hanging on 'dial tcp :3307 getsockopt: connection timed out' from a GCE VM. Use this when the proxy has no network path to the instance. Not for auth errors.
- P3018: A migration failed to apply. New migrations cannot be applied before the error is recovered from.
Fixes Prisma error P3018 'A migration failed to apply' by deciding whether the failed migration's changes actually landed, then marking it rolled back or applied with migrate resolve. Use when migrate deploy stops with P3018 and new migrati
- P3006: Migration `20240101_init` failed to apply cleanly to the shadow database.
Fixes Prisma error P3006 'Migration failed to apply cleanly to the shadow database' by finding the SQL in the migration that the empty shadow database cannot run, usually generated columns, extensions, or permissions, and rewriting it. Use
- P3005: The database schema is not empty.
Fixes Prisma error P3005 'The database schema is not empty' during migrate deploy by baselining the existing database: mark the initial migration as already applied with migrate resolve --applied instead of letting migrate try to create tab
- Timed out fetching a new connection from the connection pool.
Fixes Prisma error P2024 'Timed out fetching a new connection from the connection pool' by finding the connection leak or pool exhaustion: use a single PrismaClient instance, size connection_limit to the workload, and route serverless traff
- P1001: Can't reach database server at `YOUR_HOST`:`5432`
Fixes Prisma error P1001 'Can't reach database server' by diagnosing which part of the connection path is wrong: host, port, pooler mode, or a server that is not actually running. Use when Prisma fails to open any connection at all. Not for