kongondo Posted December 20, 2019 Share Posted December 20, 2019 4 minutes ago, gebeer said: @kongondo all is good! That ___getSelectorInfo() method was exactly what I needed. It is already live on github @gebeer You might want to clean-up some of the copy-paste inline comments that shipped with the example code from your module's code ? 1 Link to comment Share on other sites More sharing options...
gebeer Posted December 20, 2019 Author Share Posted December 20, 2019 3 minutes ago, kongondo said: You might want to clean-up some of the copy-paste inline comments that shipped with the example code from your module's code ? Done ? 1 Link to comment Share on other sites More sharing options...
szabesz Posted December 20, 2019 Share Posted December 20, 2019 18 hours ago, gebeer said: May I ask for the reason behind this? Ryan mentions some advantages of InnoDB over MyIsam in this blogpost. I'm no expert but to me it looks like for sites not enduring transaction heavy traffic MyIsam is still a bit faster, eg: http://kedar.nitty-witty.com/blog/choosing-between-myisam-and-innodb-mysql-storage-engines also, corrupted tables are less problematic, eg: https://www.knownhost.com/wiki/developmental/mysql-myisam-innodb Anyways, thanks for all refactoring efforts! 2 Link to comment Share on other sites More sharing options...
Recommended Posts