Versioned API schema
MySQL 8.4 partition key indexed column prefix rejected CREATE ALTER TABLE warning error
CREATE/ALTER TABLE that previously warned now returns an error.
Agent Quick Fix
Repair against the current MySQL 8.4 contract, then keep the change narrow and source-backed.
Product: MySQL 8.4
Current-contract area: Partition key with indexed column prefix now rejected
Likely root cause: CREATE/ALTER TABLE that previously warned now returns an error.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Check operational state and security, not a compatibility switch that weakens the server.Symptom
CREATE/ALTER TABLE that previously warned now returns an error.
Why This Happens
Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
MySQL 8.4 partition key indexed column prefix rejected CREATE ALTER TABLE warning error
site:dev.mysql.com MySQL 8.4 partitioning column prefix index partition key error
"Prefix columns in indexes are not supported for partitioning keys" MySQL
"partitioning keys" "prefix" "MySQL" "warning"
https://dev.mysql.com/doc/refman/8.4/en/partitioning-limitations.html
'prefix' in https://dev.mysql.com/doc/refman/8.4/en/partitioning-key.html