On 6/19/08, AmanKow <[EMAIL PROTECTED]> wrote:
> Absolutely. I am not pointing fingers, but throwing my two cents into > the answer to "Why PostgresSQL?" I think, given the current state of > MySQL, the problems I outlined are very strong arguments for using > postgres instead of mysql when choosing Django. I have exactly the same experience. IMHO, if you don't have a *very* good reason to choose MySQL, do *not* choose it, otherwise you will run into problems, especially if a schema evolution/migration is a significant task for you... > when I first made the Django choice, that I had made the jump to > postgres then. Unfortunatelly, we use Django application as a configuring/monitoring web based tool for large back-office application using MySQL as shared database, hence we cannot move PostgreSQL easily... Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
