WIKINDX quietly and automatically updates the database if it detects a disparity between the existing database and the required database.
Since database changes are important structural changes to WIKINDX, you should discuss the requirement for the change with other developers first.
To set this up, you need to edit the two files in update/ (createMySQL.txt and updateMySQL.txt) and the dbVersion number in INIT::dbVersion().
For example, to add a new column called v1DbConvert to WKX_config you would add the following to updateMySQL.txt (not forgetting the semi-colon!):
ALTER TABLE WKX_config ADD COLUMN v1DbConvert enum('N', 'Y') default 'N';and the following to createMySQL.txt in the statement for the WKX_config table:
`v1DbConvert` enum('N', 'Y') default 'N'The dbVersion number in INIT::dbVersion() indicates the current dbVersion required by WIKINDX. If it is greater than WKX_database_summary.dbVersion, the WIKINDX code will quietly parse updateMySQL.txt the next time WIKINDX is run in addition to incrementing WKX_database_summary.dbVersion. So, if INIT::dbVersion() is 2.0.1 (the first two figures referring to the WIKINDX version), to integrate the changes above you simply change the number to 2.0.2.
The requirement to also edit createMySQL.txt ensures that those starting afresh with a new database start off with the correct, uptodate version.