I'm struggling to understand the following: http://dpaste.com/54745/
It's a legacy database that's had the data imported with a variety of tools - not all of them very well behaved when it comes to character encoding. The offending character is a UK pound sign (163 in unicode and latin1 I believe) I initially thought that the field contained latin1 and therefore wasn't happy being saved when Django was expecting Unicode but when I construct a unicode string it compares as true to the character that is causing the problem but gives an error when I save. I then tried: p.land_value_comments = unichr(163) p.save() and got the same error. Then I tried creating a new record with just that single character in it and that didn't work either. Can anyone help me understand what's going on here? My dev server is running MySQL 4.1.21 Could that be part of the problem? regards, Andy Baker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
