I started with mysql and moved to postgres. My main reasons: 1) If you ever need to dumpdata/loaddata, you may find that postgres (correctly) defers checking of fk constraints until after the a transaction is complete. MySQL checks the constraints as each record is added, even inside of a transaction. This can break a dump/load cycle, requiring a manual reordering of records in the fixture. And can make circular references impossible to deal with at all.
2) Postgres transactions can wrap table altering, creation and deletion. MySQL cannot. This is essential if you want sane, safe migrations. I found Postgres a bit more difficult to get going, but not appreciably so. After the small amount of additional pain, it has been rock solid. pgadmin works quite well for administration tasks. So, unless my hand is forced in some way, I find postgres a better choice than mysql. Wayne --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
