Malcolm Tredinnick wrote: > If I had to guess, I would say this has to do with encoding. When the > form is submitted back to the web server, the content will be encoded > as, say, UTF-8. The length of your input string as bytes is longer than > 10 (since each of those characters is 2 bytes in UTF-8 encoding). > > This is something we are slowly fixing as part of a unicode pass through > Django, but it definitely helps to have them reported.
In fact this particular bug with maxlength was fixed almost a year ago. I think the problem here is not on Django side but on the DB side. It can happen if the DB is set up to be in some legacy encoding instead of UTF-8. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
