Richard Jones' Log: MySQL bizzaro errors

Sat, 20 Mar 2004

MySQL going senile. On the roundup-users list at the moment, we've got a most bizzare problem we're trying to solve. In a nutshell, we have a table called "_msg". We:

select id from _msg

Then for each id we get back, we:

select __retired__ from _msg where id=%s

And for some of the ids returned from the first statement, we don't get a result from the second.

Unfortunately the same statements entered straight into mysql have no problem. The same simple statements entered into a short Python script have no problem. It's just when this code is run in Roundup.

We're still looking into it, but it's mighty frustrating :(

Comment by Richard on Wed, 24 Mar 2004

Looks like a bug in the 4.1 alpha release. It consistently broke at the 650th select when AUTOCOMMIT=0 was set. I guess someone broke their transaction store...