Re:3 Common Rails + MySQL Mistakes
by Pooter on Monday February 14, 2011 @09:13PM
(#2219769)
None of these are Rails specific. Don't stick session data in a relational db if you can put it in memcache or someplace similar. Also, MySQL's query optimizer and execution engine suck (SQL server, DB2, Oracle, and PostgreSQL all handle in() queries with select statements just fine).
The select for update thing, though, sounds like a table type selection issue. Doesn't innodb handle locking at roughly row level (maybe db page)? Seems like that one is for people who stick with MyISAM. If you're doing concurrency sensitive stuff, pick a better storage engine (or more robust db).
The select for update thing, though, sounds like a table type selection issue. Doesn't innodb handle locking at roughly row level (maybe db page)? Seems like that one is for people who stick with MyISAM. If you're doing concurrency sensitive stuff, pick a better storage engine (or more robust db).