Closed walkasjesus closed 5 years ago
Do you have a solution, maybe just switching to charfield instead of textfield?
No not yet.... I do not yet understand where the problem occurs... when I restore the old model.py (from production), run the migration and update the database, it is still giving the error...
Using charfield indeed does help now, Thanx!
Fixed
some Googling learns there is a bug i.c.w. mysql: https://code.djangoproject.com/ticket/2495