The connection test says “success.” ChatGPT still cannot see the right tables—or it can see far more than intended.
SELECT 1 proves reachability. A production preflight should prove:
- the exact service identity and effective grants
- certificate and hostname verification
- visible schemas, tables, views, and columns
- time zone, SQL mode, character set, collation, and isolation
- read-only behavior and query limits
- pooled-session cleanup after errors and cancellation
- positive and negative query fixtures
Test sensitive-table access, unbounded ranges, writes, DDL, expensive joins, and cross-tenant requests. The expected result is a structured refusal—not a plausible answer.
The connection is ready only when identity, scope, session semantics, limits, and evidence all match the production contract.
Full guide: Connect MySQL to ChatGPT with a production connection preflight
