Hi Fabian, OK. That may be an easier thing to deal with.
With the implicit transactions in 0.9, if your code hits an exception it will try to rollback. Of course, if all you have are MyISAM tables, you *can't* rollback... hence the error. Personally, I wouldn't run a database without transactions, but that's just me. (I know that some folks use MyISAM to do full-text indexing as well.) The solution for an all-MyISAM database would probably be to turn implicit transactions off. Would you mind submitting a ticket to add the ability to do that? (http://trac.turbogears.org) Thanks, Kevin On 12/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello Kevin, > > no, they are all myisam tables no innodb at all. It seems that I'm not > the only one having that problem. Some tables have a fixed row format, > most have a dynamic row format, if that does mean anything. Anything > else I can check? > > Regards, > > Fabian > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
