Re: Should test failures/errors in the Django test suite when executed under MySQL be considered blockers?

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 wrote: > Hi Jim -- > > Historically, most Django core developers have

Re: Should test failures/errors in the Django test suite when executed under MySQL be considered blockers?

Thanks Jacob. At a minimum, I will at least try to wade through and open a few tickets if they aren't already open and upgrade bugs that are causing test suite errors or failures to release blocker. I did want to make sure I was not overstepping any bounds in assuming those were blockers. Cheer

Re: Should test failures/errors in the Django test suite when executed under MySQL be considered blockers?

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 th

Should test failures/errors in the Django test suite when executed under MySQL be considered blockers?

I've been trying to do a little work recently on some tickets that related to MySQL-specific issues that come up using Django (#2495 and #3615 specifically). As part of trying to get my head around resolving these, I executed the test suite in the current Django trunk using a MySQL InnoDB backe