Hi, On Friday, February 17, 2012 11:08:40 PM UTC+1, Cal Leeming [Simplicity Media Ltd] wrote: > > Could you elaborate on this a bit more? And would this affect MySQL?
Well there isn't much more to it than a "ABORT; DISCARD ALL" at the end of the session to discard changes and clean (abort) and open (broken) transaction. This way you will have a consistent connection state at every request begin. Regarding MySQL: I try to avoid it, so I can't really comment on that. Hmm - what about a documentation update, so at least people in the future > don't have to go trawling through tons of mailing lists to find this. > There is never anything wrong with more documentation, but the current solution isn't useful for other databases I guess. Aside from that, how about databases != 'default' etc… Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/klHcQbcCJ5IJ. 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.
