Would it help (in PG-world) at least if the selects where in savepoints as well?
On May 7, 10:09 am, David Cramer <[email protected]> wrote: > We hit this same issue in Postgres (it's definitely not MySQL > specific). I'm unsure of the solution or precise conditions we're > hitting it in, but I think by default we use READ COMMITTED. > > On May 7, 3:28 am, Tomasz Zielinski <[email protected]> > wrote: > > > > > > > > > I think that get_or_create is still broken, despite this > > fix:http://code.djangoproject.com/ticket/6641 > > > The details, along with a working solution, are in my answer > > here:http://stackoverflow.com/questions/2235318/how-do-i-deal-with-this-ra... > > I'm not sure if the solution is optimal, trying to INSERT first might be > > overally more expensive, but I think that something should be done with > > get_or_create. > > > Best, > > > Tomasz -- 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.
