Last modified: 2012-12-12 00:21:09 UTC
Hmm, this it the third installation I am upgrading, but the first time this has happened: php SMW_setup.php --delete --backend SMWSQLStore2 Deleting all stored data for SMWSQLStore3 completely! WARNING: This store is currently used by SMW! Deleting it will cause problems in the wiki if SMW is enabled. Abort with CTRL-C in the next 20 seconds ... 00 Deleting all database content and tables generated by SMW ... ... dropped table `62451_smw_object_ids`. ... dropped table `62451_smw_concept_cache`. ... dropped table `62451_smw_prop_stats`. ... dropped table `62451_smw_di_number`. ... etc., etc. I must admit that I used a slightly different method: 1) added $smwgDefaultStore = 'SMWSQLStore2'; to LocalSettings.php 2) ran php SMW_refreshData.php -v -b SMWSQLStore3 -fp 3) ran php SMW_refreshData.php -v -b SMWSQLStore3 4) removed $smwgDefaultStore = 'SMWSQLStore2'; from LocalSettings.php 5) ran php SMW_setup.php --delete --backend SMWSQLStore2 So what is the difference to the two updates before? I skipped a step between 1) and 2): php SMW_setup.php -b SMWSQLStore3 since I saw no sense in creating the tables and then deleting them again with step 2). I think this should not happen if you follow 1) - 5).
