On Mon, Jul 16, 2012 at 2:18 PM, Cal Leeming [Simplicity Media Ltd] <[email protected]> wrote: > Okay - anyone else want to throw their thoughts at this? > > Also - messing with the isolation levels on MySQL is really not a great > idea.. it can cause all sorts of unexpected behavior.
Just a thought -- I don't have MySQL handy to test on, but what if the savepoint occurred before the first get instead of before the create? Would rolling back the savepoint then release the row lock and allow the second get to read the row? If this works but performance is an issue, then perhaps we could dynamically order the operations according to the known isolation level? Cheers, Ian -- 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.
