Skip to content
Discussion options

You must be logged in to vote

Writing a value that isn't in an ENUM(...) set, outside MySQL strict mode, emits a silent warning 1265 'Data truncated' and writes an empty string rather than erroring — so the row keeps its old/blank status and the bug hides downstream. Grep the migration's enum() before introducing any new status string; a genuinely new value needs an ALTER TABLE first. Run strict mode so truncation throws.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Kevinchamplin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant