Re: InnoDB dropping records / MyISAM working as it should

2007-05-16 Thread Kenneth Loafman
Folks, Thanks for all the help. Not only is the code working, but my understanding of the issue has improved, thanks to this list. ...Ken -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: InnoDB dropping records / MyISAM working as it should

2007-05-16 Thread Joerg Bruehe
Hi ! Jon Ribbens wrote: On Tue, May 15, 2007 at 06:39:21PM -0500, Kenneth Loafman wrote: Interesting... guess the intent was a disconnect that would break code trying to work on MySQL, regardless of engine selected. That decision makes it two products, MySQL/MyISAM and MySQL/InnoDB with diff

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Jon Ribbens
On Tue, May 15, 2007 at 06:39:21PM -0500, Kenneth Loafman wrote: > Interesting... guess the intent was a disconnect that would break code > trying to work on MySQL, regardless of engine selected. That decision > makes it two products, MySQL/MyISAM and MySQL/InnoDB with different > semantics. Y

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Kenneth Loafman
Jon Ribbens wrote: On Tue, May 15, 2007 at 04:13:33PM -0500, Kenneth Loafman wrote: Can't tell. The docs are somewhat lacking in detail, however, if I do a db.autocommit(True) it works as it should. Will have to dig into the API code and see if that is where the semantic discontinuity lies.

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Jon Ribbens
On Tue, May 15, 2007 at 04:13:33PM -0500, Kenneth Loafman wrote: > Can't tell. The docs are somewhat lacking in detail, however, if I do a > db.autocommit(True) it works as it should. > > Will have to dig into the API code and see if that is where the semantic > discontinuity lies. The MySQL-p

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Kenneth Loafman
Ofer Inbar wrote: Kenneth Loafman <[EMAIL PROTECTED]> wrote: Sounds like InnoDB is still borked though. You should not have to use a commit unless you have started a transaction, as I understand it. The semantics for non-transaction access should be identical. Are you explicitly telling Pyt

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Ofer Inbar
Kenneth Loafman <[EMAIL PROTECTED]> wrote: > Sounds like InnoDB is still borked though. You should not have to use a > commit unless you have started a transaction, as I understand it. The > semantics for non-transaction access should be identical. Are you explicitly telling Python not to use

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Kenneth Loafman
Thanks for the tip, that worked. Sounds like InnoDB is still borked though. You should not have to use a commit unless you have started a transaction, as I understand it. The semantics for non-transaction access should be identical. ...Ken Dan Buettner wrote: Hi Kenneth - it appears that

Re: InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Dan Buettner
Hi Kenneth - it appears that you need to use an explicit 'commit' command when using InnoDB tables and Python. Something like this: try: cursor.execute("INSERT INTO Test1 (s1, i1) VALUES ('Now is the time', 5)") db.commit() Found this on http://www.serpia.org/mysql

InnoDB dropping records / MyISAM working as it should

2007-05-15 Thread Kenneth Loafman
Folks, Here's an interesting problem for you. I found a problem that did not make any sense, and in diagnosing the problem I found an issue with InnoDB vs MyISAM, so I wrote a short script to test it. The test case is a simple Open, Insert, Close series repeated 5 times with both engines.