Hmm.. That would appear to not be necessary, it's the default behavior: http://www.innodb.com/ibman.html#How_to_use_transactions
But if someone has already tried this and had problems perhaps it is... -----Original Message----- From: Emiliano Heyns [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: Re: [midgard-user] Innodb Eero af Heurlin wrote: >> If I try it and don't blow anything up I'll report back here :) >> Here's a >> posting talking about some of the gotchas which I'm hoping won't affect >> Midgard... > > One thing you must remember is that Midgard doesn't do commits, so you > must disable commit/rollback when using InnoDB. I think this was the > only problem one of my friends had when using midgard with innodb > (sympotoms: mysteriously disappearing objects). Alternately, we could make Midgard-lib end every call to the insert/update functions with a commit. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
