The reason we are using inno (important tables) for some and mysisam (logs) for others is if a failure occurs we can roll back. For instance if you are configuring menus and something had to go wrong in myisam you are screwed. The demo/no-write mode also uses roll-backs showcase a system.
Doubt we will be able to change to myisam only if we dont give up reliability. We need to weigh the pros and cons. -- You received this bug notification because you are a member of PHPDevShell, which is subscribed to PHPDevShell. https://bugs.launchpad.net/bugs/1039162 Title: myisam instead of innodb? Status in Open Source PHP RAD Framework with UI.: New Bug description: In our database, some tables are myisam some are innodb. However innodb is hard to backup, unreliable in case of crash, and can't be repaired. Considering we don't really need transactions and we don't use foreign keys and triggers, I suggest we use only myisam which is very easy to backup and to repair To manage notifications about this bug go to: https://bugs.launchpad.net/phpdevshell/+bug/1039162/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~phpdevshell Post to : [email protected] Unsubscribe : https://launchpad.net/~phpdevshell More help : https://help.launchpad.net/ListHelp
