On 16 heinä, 23:18, "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.
The idea is that one could use different isolation levels when wanted, something like @commit_on_success(isolation='READ COMMITTED'). This should come with two warnings: - You should know what you are doing. - Django is designed to work in the default isolation level - all guarantees are off when using different isolation levels. I must say that the real reason why I would like the above implemented is the "true serializable" isolation level in PostgreSQL 9.1+. It would be very useful in many of my projects... But, this is a much bigger change, and one that I don't expect to happen soon (if ever). Definitely not a quick way to solve this issue. - Anssi -- 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.
