On Thu, Jun 19, 2008 at 6:23 AM, AmanKow <[EMAIL PROTECTED]> wrote: > > I have to disagree that Django supports these backends equally well. > I've just been bitten badly by the 'dumpdata <app>' 'loaddata <app>' > problems with MySQL and innodb. I originally decided to go with MySQL > (familiarity, for the most part). Using MyIsam tables is not an > option for me, I need the transaction support.
Lets be clear here - the problem you are describing is fundamentally MySQL's problem, not Django's. MySQL doesn't interpret the standard right, and doesn't provide for an easy workaround. There isn't much Django can do in this case. This is an example of what Tim was talking about - MySQL is still adding features and fixing problems with their SQL implementation. If you choose a piece of infrastructure, you have to accept the limitations of that infrastructure. Any database backend will have strengths and weaknesses; the fixture loading problem is one of MySQL's limitations. > Of course, it quickly becomes obvious that editing the output of > dumpdata is a bear with any significant amount of data or an app of > any complexity. As there is no way to specify the order of tables for > dumpdata, and apparently dumpdata doesn't attempt to dump referenced > tables first, this is quite a problem for MySQL users. Ordering tables is a partial solution, but it won't work in the general case. However, something would be better than nothing, and there is something to be said for making serialized output ordered for purely aesthetic reasons. If someone (cough cough... hint hint) were to submit a patch to implement table ordering on serialized output, I'd have no problem committing such a patch. > Speaking of > evolving, django-evolution has many issues with MySQL versus > postgress. I've therfore decided to bite the bullet and switch to > postgres... (for those not aware - I'm a core developer of Django Evolution. These next comments are from me wearing my Evolution core developer hat) Django Evolution is a slightly different beast - Django Evolution isn't part of the core Django project, and if you read the FAQ, I don't make the claim that MySQL is equally supported under Django Evolution - in fact, I clearly state that MySQL is a work in progress, simply due to my personal priorities. I have also said on many occasions that I would like to fix this situation, but I am only one man, and I only have so much time to give. I will gladly accept any patch to Django Evolution that improves MySQL support (and I have done so on a number of occasions in the recent past). > In short, I don't think it is fair to say that Django supports all db > backends equally. I wish that early on, when choosing Django, I had > been led definitively down the postgres path. If a bug is found in Django's MySQL, we are committed to fixing it (if it can be fixed). The ticket just needs to work through the triage process. There is only 1 ticket in the "Ready for Checkin" list that is MySQL specific, and I'm not completely convinced it's the right solution. If MySQL were a non-supported platform, this list would be longer. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
