On Oct 24, 10:27 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> so is this a legacy database - meaning a database which had data > before you upgraded to unicode django? In that case, we have seen in > postgres that the old data is b0rked and needs to be reentered, > otherwise it wont work. You need to either re-enter the data or write > scripts to transform the b0rked data. > That sounds rather worrying, from someone who has a big database and will soon be upgrading to unicode django. Do you have any more details? Was it simply due to a database encoding change (in which case databases which are already in utf-8 should be ok?), or did you hit some more fundamental problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
