j.silver Posted December 4, 2016 Share Posted December 4, 2016 Dear all, For photo gallery tables (named: gallery_album, gallery_image, gallery_relation), I have seen a recommendation to use InnoDB engine in preference to MyISAM. I thought MyISAM would be the choice for all tables but tables for transactions. Do you agree with the recommendation to using InnoDB for photo gallery tables and why? Link to comment Share on other sites More sharing options...
davej Posted December 4, 2016 Share Posted December 4, 2016 Is there a need for these images to be secure? Link to comment Share on other sites More sharing options...
j.silver Posted December 4, 2016 Author Share Posted December 4, 2016 The example is not telling whether or not the images must be secured. Link to comment Share on other sites More sharing options...
davej Posted December 4, 2016 Share Posted December 4, 2016 InnoDB has a better reputation -- but do you really need to store the images in a database? If you don't need the images to be secure then you can simply store them in the filesystem. Link to comment Share on other sites More sharing options...
j.silver Posted December 5, 2016 Author Share Posted December 5, 2016 Better reputation in what scene? My understanding is that InnoDB takes more space in the server and is slower than MyISAM. Link to comment Share on other sites More sharing options...
davej Posted December 5, 2016 Share Posted December 5, 2016 You can search for yourself... https://www.google.com/?gws_rd=ssl#q=innodb+vs+myisam Link to comment Share on other sites More sharing options...
justsomeguy Posted December 5, 2016 Share Posted December 5, 2016 The fact that InnoDB supports transactions and foreign keys and MyISAM does not is enough for me to always use InnoDB. The table-level locking that MyISAM does has also brought applications to a halt, where many people are waiting to write to a particular table that one person is selecting data from even though they are working with different rows. MyISAM still locks the entire table. Link to comment Share on other sites More sharing options...
j.silver Posted December 5, 2016 Author Share Posted December 5, 2016 Many thanks davej and justsomeguy Can I conclude that from now on I should use InnoDB in all types of tables and never use MyISAM, or there is still usefulness in MyISAM for certain types of tables? Link to comment Share on other sites More sharing options...
justsomeguy Posted December 5, 2016 Share Posted December 5, 2016 If your site is 99% select queries and very little insert, update, or delete, and you don't care about enforcing transactions or table relationships, then you can use MyISAM. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now