Why was MyISAM a fix to this problem caused by InnoDB?

Most probably because you never called commit MySQLdb (I suppose that's the module you're using) automatically starts a transaction for every connection you make to your database server. All the insert queries work just fine and increment the auto_increment counter, but you never see the results from phpMyAdmin because InnoDB isolates its connection from the changes made via python. If your Python script disconnects and no commit call was made, the transaction is rolled back and no changes (apart from the incremented auto_increment counter) are persisted.

See if a db.commit() (assuming db is the connection object) helps Also see PEP 249 on database access in Python.

Most probably because you never called commit. MySQLdb (I suppose that's the module you're using) automatically starts a transaction for every connection you make to your database server. All the insert queries work just fine and increment the auto_incrementcounter, but you never see the results from phpMyAdmin because InnoDB isolates its connection from the changes made via python.

If your Python script disconnects and no commit call was made, the transaction is rolled back and no changes (apart from the incremented auto_increment counter) are persisted. See if a db.commit() (assuming db is the connection object) helps. Also see PEP 249 on database access in Python.

Another factor I didn't think of when posting the question: It was actually the first time I had an INSERT statement anywhere in the application. That should have been a clue. – Trindaz May 30 at 4:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.