#10994: Flay page content with unicode causes fatal error but data is still
commited
-------------------------------------------+--------------------------------
Reporter: [email protected] | Owner: nobody
Status: closed | Milestone:
Component: django.contrib.admin | Version: 1.0
Resolution: invalid | Keywords: uniode mysql
flatpages
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by kmtracey):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
It sounds like the character set for your table is the MySQL default
latin1. When you try to store some Unicode value that cannot be
represented in latin1 you will get "incorrect string value" from MySQL,
because there simply is no way to represent some Unicode data in latin1.
There is no bug with Django here, the problem is your database. The fix
is to convert your table to use utf8 as the character set. Here's the
MySQL doc for how to do that: http://dev.mysql.com/doc/refman/5.1/en
/alter-table.html. Specifically, see the "CONVERT TO CHARACTER SET" part.
--
Ticket URL: <http://code.djangoproject.com/ticket/10994#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
