Timeline for answer to MySQL "incorrect string value" error when save unicode string in Django by gerdemb
Current License: CC BY-SA 3.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 28, 2019 at 14:06 | comment | added | Michal Przysucha | This solved my problem. The only change I did was to use utf8mb4 and utf8mb4_general_ci instead of utf8 / utf8_general_ci. | |
| S Jan 4, 2016 at 14:59 | history | suggested | Community Bot | CC BY-SA 3.0 |
current one is scrollable and difficult to read and copy,i just divided into two lines.With Proposed :Its easy to read and copy
|
| Jan 4, 2016 at 14:06 | review | Suggested edits | |||
| S Jan 4, 2016 at 14:59 | |||||
| Sep 9, 2011 at 23:24 | comment | added | madprops | This worked for me as well, using mysql with the defaults, in a TextField model. | |
| Jul 18, 2011 at 17:43 | comment | added | markpasc | Ugh, I changed all the character sets on everything I could until I really re-read this answer: columns can have their own character sets, independent of the tables and the database. That's crazy and also was exactly my problem. | |
| Jan 25, 2011 at 12:28 | history | answered | gerdemb | CC BY-SA 2.5 |