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?
On Thursday, March 21, 2013 9:58:37 AM UTC-4, Alan Johnson wrote: > > I want to echo the support for Postgres. I find it to be a bit more arcane > than MySQL, but even in an extremely DB intensive app, Django's ORM is so > slick that I rarely have to muck around in Postgres land. I think it's * > slightly* better supported by Django, if you need to use things like > distinct(), and other tiny little differences. Two Scoops of Django, which > someone mentioned earlier, has become like a holy book to me when it comes > to deployment, and they endorse Postgres as well. Navicat is indispensable > for getting out of the ORM and seeing what the hell is going on in your DB, > as I'm sure you already know. For another migration method, I'll also throw > out the option of djang-extensions dumpscript ( > http://pythonhosted.org/django-extensions/dumpscript.html), which > generates the ORM commands to create your database, and can be used for > migration. > > > On Monday, March 18, 2013 11:30:35 AM UTC-4, frocco wrote: >> >> Hello, >> >> What is the recommended database for django? >> >> I have used MySQL, but am interested in Postgres. >> >> Thanks >> > -- 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.
