Comment 2 for bug 1330638

So what's the plan with these "lock wait timeout" bugs?

Is the plan to A) squash each one separately, or B) squash the single underlying issue?

If A) it will mean preventing all eventlet-yielding calls while a transaction is open. I _think_ I can write a pylint check to find those cases for us.

If B) then I'd like to close all of these as duplicates of bug 1350149 - or some other central description of the problem.

I feel rather strongly that (B) is the right answer here, but the fact that multiple bugs were opened without linking to a single cause - and the general resistance I've been getting trying to abandon mysqldb(*) - makes me thing we (plural) want to go with (A) instead.

Thoughts?

(*) See for example Eugene's comment on bug 1350149. Not trying to highlight any particular incident, but I encountered such a total lack of enthusiasm from all directions for (B) that I went and worked on something else instead.