Hancock, David (DHANCOCK) wrote:
> We are strongly considering migrating from MySQL to PostgreSQL, but 
> there seem to be enough differences between the two that I'm pulling my 
> hair out. I know this is somewhat off-topic, but has anybody got some 
> resources for the conversion process?
> 
> I'd love it to be as simple as a dump-and-restore, but so far, no silver 
> bullet has emerged. Things I've tried:
> 
>     mysqldump --compatible=postgresql # not so compatible
>     dump-db.py from djangosnippets.org # many data differences
>     hand-editing dumped SQL # too much work, nonexistent foreign key values
>     manage.py dumpdata # chokes on Decimal(0.00) datatype, not sure how 
> to load output anyway

Well, that would be because MySQL is effectively broke in many weird 
ways. Your best bet is to recreate your model in postgresql, initialize 
that model and move the data over relation by relation.

Joshua D. Drake


> 
> Thanks in advance, and
> Cheers!
> -- 
> David Hancock | [EMAIL PROTECTED]
> 
> > 


-- 

       === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to