On Thu, Jul 7, 2011 at 5:05 AM, Jim D. <[email protected]> wrote: > Are any core devs interested in taking a closer look at the current patch on > this ticket (https://code.djangoproject.com/ticket/3615)? It's been through > several rounds of revision after discussion here and on the ticket comment > thread.
Interested - most certainly. The issue (as always) is finding the time :-) I'm certainly grateful for your efforts; this is a long standing issue that I'd love to see addressed; I'm just not in a position to commit to anything. I'll put this on my list of things to look at, but I'm not getting a whole lot of time to look at that list at the moment. > * There's a DB feature can_defer_constraint_checks . I couldn't find much > by way of documentation or or usage of this feature. But I was trying to > figure out if the work we are doing here is what this feature refers to, and > if so, if we should be marking this as True for MySQL and SQLite with this > implementation. I'm not sure there is other behavior that is required or > expected in that attribute. Anyhow, that might also be a path forward for > the issue I raise above (ie. we could skip the test if > can_defer_constraint_checks is not True). This feature flag exists essentially to verify whether MySQL InnoDB is currently in use. It isn't used during normal runtime; it's purely a test skipping flag. It's used to identify tests that need to be skipped because the test data requires a circular reference which (historically) hasn't been possible under InnoDB because constraints aren't checked. Essentially, this feature flag shouldn't need to exist at all; it only exists so that InnoDB passes the test suite without errors. If we are able to resolve the issue that allows MySQL to use forward references in data, then this feature flag shouldn't be required at all. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
