I’ve got some valuable help on this forum , so want to pay back a bit and give some of you information, about the MySQL tables in SC modules.
I HOPE THIS POST WILL HELP SOME OF YOU AND CLARIFY SOME PROBLEMS WITH SCRIPT CASE MODULES.
I just discovered something very ugly Security module. This probably can’t be qualified as bug but rather missing super important feature OR poor design. The problem lies in the database and its limitation.
This basically prevents creating new module if your server default database engine is set to MyISAM. This is my case and unfortunately the hosting provider states it cannot be changed. Since this is shared server (I use). Whoever did this setting default was an ignorant, but there is nothing I can do about it.
So now SC pops up an error half way when trying to create tables and it stops (after creating 4 tables).
I tested the same locally and there is no problem when the default engine is set to InnoDB.
I have an open ticket about this and Netmake makes so nonsense statements to use option for “existing tables” , while the half of them was not created. Basically we need a setting in the SEC.MOD procedure to set default engine for MySQL/MariaDB.
This requires simply to modify the CREATE command, but nobody but NETMAKE has access to change it.
So far the only workaround is to create a connection locally, and create tables. Then move these tables over to where one wants to continue and use them for development. This has some problems though.
If Netmake change the structure or you want to create new project you have to do this manual workaround again and again… which simply adds extra time, frustration and room for errors.
They have change some Keys in the updated SEC tables and now the MyISAM is popping out errors upon creation. Not only this but MyISAM does not support transactions and Relational Constraints, so it is kinda like going back to WindowsXP (good but limited). Another words even changing the engines manual will not be enough.
I have had some issues with the SEC.MOD in the past, when all of this sudden things got corrupted, and I could not figure out why. Most likely this was a problem and I have not noticed the engine for SEC_ tables was set to MyISAM.
Because of that I wasted tons and tons of time.
We need to push NETMAKE to implement InnoDB as default engine in the table creation. Better yet we should have a choice of the engine. This would also apply to NOTIFICATIONS and LOG tables. All of them will be screwed on some servers.
I wasn’t paying attention to the engine, and having 300+ tables is easy to miss that some are different.
Now I suggest to go and check your default engine.
Now I have to create the tables locally, so I have full control. Which eats up my time and slows down the work. If somebody has some kind of solution to this problem, please share it here.
