MX Administrative Interface: Difference between revisions

MX Administrative Interface (view source)

Revision as of 12:39, 12 July 2020

146 bytes added , 12:39, 12 July 2020

m

→‎MySQL settings

Sfws

5,838

edits

@@ Line 262: / Line 262: @@
 Cumulus MX includes functionality not in Cumulus 1, and this is one example of a new feature.  It is designed to automate updating of MySQL databases whose schema has each table based on one of the Cumulus log files. This MX feature was developed from [[ImportCumulusFile|this script]] for Cumulus 1.
-'''IMPORTANT''' The MX automatic standard updates described below only work if the database table they are updating has columns named exactly as defined in the standard update. All the MX updates will work even if you have defined additional columns in the standard tables and update those in a separate process. But when extra columns are added as at versions 3.6.0 and 3.7.0, the MX updates will NOT work unless you have added the extra columns introduced in those releases with correct names. For those releases, the release announcement includes a script to run to add the extra columns needed for those (and subsequent) releases.
+'''IMPORTANT'''
+*The MX automatic standard updates described below only work if the database table they are updating has columns named exactly as defined in the standard update.
+**The order of those columns does not matter, both CumulusMx.exe and ExportMySQL.exe use column names in their INSERT IGNORE statements.
+*All the MX updates will work even if you have defined additional columns in the standard tables and update those in a separate process.
+*But when extra columns are added as at versions 3.6.0 and 3.7.0, the MX updates will NOT work unless you have added the extra columns introduced in those releases with correct names.
+**For those releases, the release announcement includes a script to run to add the extra columns needed for those (and subsequent) releases.
 ==== Brief background on SQL ====