Timeline for Choosing MyISAM over InnoDB for these project requirements; and long term options
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2016 at 22:29 | comment | added | Craig Tullis | 2000 write to a database is a lot? That's kind of funny. It's kind of like buying a weak little Gremlin hatchback instead of a pickup, then saying that 400 pounds of bricks in the back is a lot. ;-) | |
| S Jul 3, 2014 at 6:25 | history | suggested | elixenide | CC BY-SA 3.0 |
Typographical errors
|
| Jul 3, 2014 at 5:21 | review | Suggested edits | |||
| S Jul 3, 2014 at 6:25 | |||||
| Sep 30, 2012 at 15:23 | comment | added | user12940 | Hmmm... Then I guess MyISAM is bad for my application after all; and since I've sorted out the InnoDB performance issue, I will be using it. Thanks! | |
| Sep 27, 2012 at 21:35 | comment | added | Luke101 | Its easy to fix a MyIsam corrupted table. When It gets corrupted just do a repair; Done. 2000 writes is a lot if your myisam database is getting hit hard. It will slow down other connections trying to do a write. | |
| Sep 27, 2012 at 6:54 | comment | added | user12940 | "MyIsam tends to get corrupted at least once a month...high traffic website", uh, that's scary! Does "traffic" here mean only the majority reads for my site, or does it also include my comparitively low 2000 writes? | |
| Sep 26, 2012 at 15:21 | history | answered | Luke101 | CC BY-SA 3.0 |