myisam instead of innodb?
Bug #1039162 reported by
Greg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| PHPDevShell |
New
|
Wishlist
|
Unassigned | ||
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
| Changed in phpdevshell: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| TitanKing (titan-phpdevshell) wrote | #1 |
To post a comment you must log in.
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.