There's two balancing forces here - I don't want to delay the release as we always do that, but then again we always make sure we ship correct, not on time.
I'll investigate this as much as I can this week, and see if I can get the dump-and-restore-to-fixture stuff working, as I think that's the best solution we have here, as it "emulates" the right behaviour on databases with no transactions and should do the right thing for TransactionTestCases. I've opened a ticket here: https://code.djangoproject.com/ticket/22487 Andrew On Tue, Apr 22, 2014 at 2:02 AM, Christian Schmitt <[email protected] > wrote: > Hm, I’m not a core developer, but i wouldn’t prefer the documentation that > explains the edge cases. > > As Russel Keith-Magee already said that Django is a tool that ensures > quality. > We should definitly make a Ticket and try to clear that thing up before > the 1.7 release. I mean this is not a new feature since Django 1.7 should > already support Data Migrations even in TestCases. > > Also I don’t think that people will read every part of the documentation. > I don’t know how many people will use Migrations and especially Data > Migrations and rely on Django’s TestCases but i don’t think that i’m the > only one, so the 1.7 release wouldn’t be that useful for these people as it > will be to other people that don’t use data migrations and/or don’t test > their applications. > > — > Best Regards > > Christian Schmitt > [email protected] > > > > > Am 22.04.2014 um 03:22 schrieb Russell Keith-Magee < > [email protected]>: > > deferred > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1upf4tve3ZW8Yufb8QCL3Q8VJdmpDTSbY%3DsQMT40a9y0ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
