TurboGears is heading in an 'everything is wrapped in a transaction' model, which is fine. MySQL supports transactions only if the tables involved are InnoDB tables. SQLObject does not know how to create InnoDB tables, but can use them just fine once they exist.
This means that the norm of creating your model and then using 'tg-admin sql create' will not work for creating the needed InnoDB tables; the tables created will be of the non-transactional MyISAM type. Instead, it will be necessary to figure out what SQLObject would do (probably using debugging output), and then do it manually, with just appending 'ENGINE=INNODB' onto the CREATE statements. This sure breaks the 'ease of use' paradigm for TurboGears. What work is being done to address this problem?
