<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Do you know what type of database engine you are using in MySQL for the " mythconverg" data base. I only ask this as a long while ago a user had the "InnoDB" engine instead of the usual "MyISAM". Apparently "InnoDB" supported database roll-back so every jamu write to the data base was being rolled back.<br>
</blockquote></div><div><br>You are correct, I'm using InnoDB.<br> </div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Now this was fixed a long time ago in the Python bindings (since Mythtv 0.22+fixes) but I wonder if this is related as no other users do not seem to have this issue.<br></blockquote></div><div><br>I'm betting you're right here too. I put breakpoints in the bindings and stopped just before the the execute for the update. If I evaluate the string the connect is about to execute (ie the "UPDATE ...") and try it in the mysql client then it works ok. The bindings don't work however.<br>
<br></div>Tonight I'll try and alter the table back to myisam and see if that helps.<br><div>
<br><br></div></div></blockquote><div><br>I converted the table to MyISAM and things now work correctly. Looks like you were right about the InnoDB aspect.<br><br>Where do you want to go from here? I'm guessing you can probably reproduce this on your own at this point. Alternatively I'm happy to try any patches/ideas you might have.<br>
<br>--Jack <br></div></div>