You don't have to have the databases set up at the same time for the django-extensions dumpscript method (nor for the dumpdata method). I haven't used it myself, but as I understand it, the script will contain the data you need.
1. Create the script with existing MySQL running 2. Reconfigure settings for PostgreSQL 3. Run the script I'm not saying it's better than any other method, just throwing out the option. On Thursday, March 21, 2013 3:49:33 PM UTC-4, Shawn Milochik wrote: > > On Thu, Mar 21, 2013 at 3:44 PM, Lachlan Musicman > <dat...@gmail.com<javascript:>> > wrote: > > Frocco, > > > > No, he's saying you can have two databases set up at the same time. > > You can have X databases (I presume). > > > > Cheers > > L. > > > > On 22 March 2013 01:13, frocco <far...@gmail.com <javascript:>> wrote: > >> Hi Alan, > >> > >> so you are saying I should connect django to mysql first and then > generate > >> the script. > >> Then connect django to postgresql and do the import? > >> > > > Actually, I think that's exactly what he meant. If MySQL is working, > do the dumpdata commands. Save the output. Change your settings to use > Postgres. Then run the loaddata commands. At that point, you've > successfully replaced MySQL with Postgres. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
