This doesn't work as expected. I tried the migration with dumpdata month ago. The problem is, that mysql and postgres writes another, incompatible boolean values. I believe sqlite and postgres has the same problem! I reworked the dumpdata output-file. In my case this was possible, because the amount of data was not too big
On 30 Okt., 08:44, David Christiansen <[EMAIL PROTECTED]> wrote: > Why not just dump the data using manage.py dumpdata, switch your > settings file to point to the new DB, run syncdb, and then use > manage.py loaddata to get it all back? That should be pretty easy. > > -David Christiansen > > On Oct 30, 2:39 am, "Naitik Shah" <[EMAIL PROTECTED]> wrote: > > > I looked around but didn't find anything obvious or simple. This is a live > > Django app with data in MySQL which I want to migrate to PostgreSQL. > > Suggestions? (Before I do my own thing :)) > > > -Naitik --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
