On Wed, Aug 8, 2012 at 8:13 AM, Cal Leeming [Simplicity Media Ltd] < [email protected]> wrote:
> Does anyone else have any input at this stage?? > > It seems to me that the most appropriate way forward is a documentation > update which explains that get_or_create() is not atomically safe across > all databases, and may need a commit() before hand, or a read isolation > change (with warnings about both). > > The docs should note that READ COMMITTED isolation level, or database-level autocommit of every query, is required for get_or_create() to work properly under MySQL. Recommending an alternative of a commit beforehand strikes me as wrong. Karen -- 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.
