Execute SQL instructions using a MySQL-flavored syntax.
sql package installation plugin expects a relative path to a
WoltLab Suite Core uses a SQL parser to extract queries and log certain actions. This allows WoltLab Suite Core to revert some of the changes you apply upon package uninstallation.
The logged changes are:
ALTER TABLE … ADD COLUMN
ALTER TABLE … ADD … KEY
It is possible to use different instance numbers, e.g. two separate WoltLab Suite Core installations within one database.
WoltLab Suite Core requires you to always use
blog1_blog in WoltLab Suite Blog), the number (
1) will be automatically replaced prior to execution.
If you every use anything other but
1, you will eventually break things, thus always use
WoltLab Suite Core will determine the type of database tables on its own:
If the table contains a
FULLTEXT index, it uses
InnoDB is used.
WoltLab Suite Core cannot revert changes to the database structure which would cause to the data to be either changed or new data to be incompatible with the original format.
Additionally, WoltLab Suite Core does not track regular SQL queries such as
WoltLab Suite Core does not support trigger since MySQL does not support execution of triggers if the event was fired by a cascading foreign key action. If you really need triggers, you should consider adding them by custom SQL queries using a script.
CREATE TABLE wcf1_foo_bar ( fooID INT(10) NOT NULL AUTO_INCREMENT PRIMARY KEY, packageID INT(10) NOT NULL, bar VARCHAR(255) NOT NULL DEFAULT '', foobar VARCHAR(50) NOT NULL DEFAULT '', UNIQUE KEY baz (bar, foobar) ); ALTER TABLE wcf1_foo_bar ADD FOREIGN KEY (packageID) REFERENCES wcf1_package (packageID) ON DELETE CASCADE;