[BUG]: drizzle-kit pull fails silently on MySQL 5.7 because introspection queries information_schema.check_constraints

[SevenJoker]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

0.45.2

What version of drizzle-kit are you using?

0.31.10

Other packages

No response

Describe the Bug

drizzle-kit pull fails on MySQL 5.7.26 even though the database connection is valid and table/column/index introspection succeeds. After local debugging, I found that MySQL introspection queries information_schema.check_constraints, but this table does not exist in MySQL 5.7, so the command fails with ER_UNKNOWN_TABLE: Unknown table 'check_constraints' in information_schema. The CLI then exits with code 1 without surfacing the real database error, which makes the failure look silent. This seems to be a MySQL 5.7 compatibility issue in pull, plus missing error reporting for the underlying query failure.

[molloyzak13]

reply_target: #5921

The query that hits information_schema.check_constraints is in drizzle-kit/src/serializer/mysqlSerializer.ts, around line 951. It is a JOIN on table_constraints + check_constraints to pull CHECK clauses for introspection. That check_constraints table was added in MySQL 8.0.16, so it does not exist in 5.7.

The fix is straightforward: wrap the check_constraints query in a try/catch. If ER_UNKNOWN_TABLE (error 1109) comes back, return an empty CHECK constraint map and let the rest of introspection finish. Tables, columns, indexes, and FKs all introspect fine on 5.7 — there are simply no CHECK constraints, which is correct. The FK introspection in the same file already follows this pattern (line 788–854), silently catching and continuing on FK lookup failures. Same approach, one block up.