W dniu piątek, 2 grudnia 2016 12:05:11 UTC+1 użytkownik Mateusz Mikołajczyk napisał: > > What would you say about checking which CRUD operations were executed > within atomic() call (in order to serialize them and save into a special > model for databases which don't support this functionality) ? Is it > realistic? >
It would likely break the promise that distributed two-step transactions give you: that once all statements are prepared the transaction is unlikely to fail during commit. In this case the commit would mean "start over and try to repeat my steps" at which point any of the recorded statements is likely to fail constraint checks. (Even more so if your code used get_or_create().) Also how would relations work? You begin a transaction, create a Foo instance and the returned PK is 5. You assign it to child models. At this point the transaction is saved and rolled back. During replay the insert returns PK = 7, at this point there's no way to detect that some of the stored fives should now be treated as sevens while some should remain fives. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/098bbb3a-1ba0-42e5-8b75-441474981855%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
