Better patch to fix #5783

[amax@…]

Hi,

Earlier we contributed a patch to solve #5783, which was accepted and merged into trunk. With more experience, we have found the attached patch to be better. The first patch solved the original bug most of the time, but it did sporadically show up again. This new patch is more thorough; we've used it for about four months, and so far (knock on wood) the error has not reoccurred.

This try-catch approach was considered at one point (if you dig into the mailing lists), but at the time it appeared not to be necessary. I think now that it is.

-Aaron

[amax@…]

patch: purportedly better fix for #5783

[amax@…]

patch: purportedly better fix for #5783 (previous upload of this name was incorrect, this one is the right patch)

[anonymous]

Just to clarify, the patch labeled trac_better_mysql_fix.diff is not correct. My mistake - I uploaded the wrong patch. The correct patch is trac_better_mysql_fix.2.diff .

[cboos]

Thanks for the patch!

[cboos]

Applied in r6510 for trunk and r6511 for 0.10.5dev.

I removed the non-global import MySQLdb statements, which IIRC also can lead to trouble. I tested the modified patch on trunk, but not on 0.10.5dev, I hope everything is right there.