Hi there
Our hosting partner is running PHP 5.6 at the moment and will change to PHP 7 sometime next year. We are planning to update several EE2-projects to EE3 with this.
One particular project is an MSM-group of 5 websites, which is going to expand to 6 websites in the future and has a lot of fields. So the exp_channel_data-table is over 1000 db columns wide, that is why we had to change the tables from InnoDB to MyISAM a few years ago.
But EE 3 needs InnoDB as new table engine. So we can’t update this project because MyISAM is not the standard anymore? What could be a solution for large sites like this?
Thanks for an answer or idea!
Ok, thanks for this one! I am a bit eased off now …
But what interests me also is that all channel field data out of all MSM sites is in one table in the db, is this still the fact with EE3?
Why not use one table per MSM site in EE3, so this scaling problem with InnoDB wouldn’t be one?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.