Please Log in or Create an account to join the conversation.
I see, at this time I unfortunately don't have anything further to suggest except re-evaluate your field usage and delete fields you may not need. This is a known issue we're currently working to fix so I don't have a definitive fix at this time. This is a MYSQL limitation that we'll have to find a way to workaround and changing the storage engine should've worked, but for some reason it isn't for your install.yes i changed that, all _comprofiler tables has innodb engine, but some others components are myisam groupjive, adblog etc...
Yes, that's fine as those are just rows for select fields."f3mps_comprofiler_field_values" has 2039 rows,its OK?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.