Warning: Creating default object from empty value in /www/htdocs/v030397/mysql-qotd/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 4991
Warning: Creating default object from empty value in /www/htdocs/v030397/mysql-qotd/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 4993
Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/v030397/mysql-qotd/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:4991) in /www/htdocs/v030397/mysql-qotd/wp-includes/feed-rss2-comments.php on line 8 Comments on: Question 54: Which are scenarios for MyISAM tables?
http://mysql-qotd.casperia.net/archives/404
mysql 5.0/5.1 questions for learning purposesFri, 06 Aug 2010 16:56:36 +0000http://wordpress.org/?v=abchourly1By: plogi
http://mysql-qotd.casperia.net/archives/404/comment-page-1#comment-63
plogiMon, 31 May 2010 17:49:11 +0000http://mysql-qotd.casperia.net/?p=404#comment-63<b>
a c d
MyISAM is fast, and the table-locking is of little consequence for read-heavy tables.
It stores data in an efficient way and offers index-compression.
If your tables are written into and read from all the time by many connections,
then MyISAM is not the right choice.
</b>
a c d
MyISAM is fast, and the table-locking is of little consequence for read-heavy tables.
It stores data in an efficient way and offers index-compression.
If your tables are written into and read from all the time by many connections,
then MyISAM is not the right choice.
]]>