On 22/10/10 17:34, Kevin Monceaux wrote: > I think the OP was referring to mysqldump's --compatible option which > one could use, for example, as mysqldump --compatible=postgresql ...
Doesn't Work, btw. (really doesn't help much, at least in my experience - you just end up with dump that's neither mysql nor postgresql compatible). If you do go the text dump conversion route (which I don't recommend in the first place!), you're better off using mysqldump to output a mysql dialect dump that can then be munged more comprehensively into postgresql dialect by a third party tool e.g. http://pgfoundry.org/projects/mysql2pgsql/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
