And if is a real problem in the MySQL support, I'm willing to look into it. I use it in production. You might have to poke me directly but I am trying to pay attention lately.
On Thu, Jun 23, 2011 at 5:53 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hi Jim -- > > Historically, most Django core developers have been PostgreSQL users > (and advocates to some degree). This has meant that, yes, MySQL > support has lagged behind. It's not that MySQL support isn't > considered important, but it is a matter of priorities. I, at least, > am going to prioritize the database that I actually *use*. > > That said, I'm embarrassed by how bad the state of things is (though I > can't reproduce your need-to-modify-the-tests-even-to-get-them-to-run > thing), and we should certainly be doing better. It'll take someone > with the motivation to plink away at the MySQL issues, and I would be > thrilled if that's you. > > And yes, if the test suite isn't even *running* that should be > considered a release blocker! > > Jacob > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- Question the answers -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
