pculture/mirocommunity — comment on commit a1cf594f9ca2f5700119cfccaa9fdc37e08b9b80
File:  line 0
By paulswartz:

I was pretty surprised, but it's definitely happening. When testing imports
of http://blip.tv/amherstmedia I hit this issue nearly every time. It could
be how my MySQL server is configured, but I haven't done anything to
configure it so presumably its a problem with the default configuration.

My guess is that if two workers update the value around the same time, they
both increment it to the same value and MySQL doesn't recognize them as a
conflict. Django 1.4's select_for_update() might resolve this, but that's
for a future release.

-p
--
Paul Swartz
This message sent from a mobile device