mysql table engine / xbmc transaction handling

Hi,

My question is about how xbmc handles transactions when scanning/updating the library.

In my setup the sql-server had MyISAM as default storage engine.
So when xbmc created all the tables, they was created as MyISAM tables.

And when looking at the logfile when xbmc adding new content to the library, the log says it starts transaction, and then commits the transaction to the database.
But, MyISAM tables does not handle transactions.
So how does xbmc do this?

And to continue, what impact would changing the tables to InnoDB do?
By changing to InnoDB, one would get true transaction support.
From one thread in this forum, i did read that someone got the library faster by changing FROM InnoDB to MyISAM.
But apart from that, I have not found any other information.

And regaring the speed issue when using InnoDB, MySQL has support of running InnoDB tables in memory just to speed things up.
Historic MySQL says MyISAM should be faster than InnoDB, but that is not the case in recent versions of MySQL.