2021-03-14, 12:23 PM
Currently the code for $db->add_column and $db->modify_column do not actually check if the column type or definition are valid for the database engine that is used. SQLite doesn't have VARBINARY, but instead is called BLOB as one example. I propose creating another method in the database classes that actually validates what column types and attributes are available. If the column type is not supported, then it returns the equivalent for that database engine. Any attributes that are not supported such as UNSIGNED are stripped out from the definition as well.
The reason for this suggestion is that many plugins on the extend site only support MySQLi. This leaves users that don't have that available or who prefer to use a different database engine a lot less options and would generally need to hire a developer to make changes to make the plugin work.
The reason for this suggestion is that many plugins on the extend site only support MySQLi. This leaves users that don't have that available or who prefer to use a different database engine a lot less options and would generally need to hire a developer to make changes to make the plugin work.