Dear SMW developers,
I suspect that SMW issues queries altering tables (mainly, OPTIMIZE) to SQL backend every time that a query is made to wiki API, including automatically updating recent changes; as if SetupStore.php is being launched again and again. That happens because something is wrong with the upgrade key.

In fact, SetupStore.php has been run on container startup, and only then php-fpm started. There is no cron in the container.

Is this so, and how can this be switched off? Updating the database without being explicitly told to do that is definitely wrong.

Dear SMW developers,
I suspect that SMW issues queries altering tables (mainly, OPTIMIZE) to SQL backend every time that a query is made to wiki API, including automatically updating recent changes; as if SetupStore.php were being launched again and again. That happens because something is wrong with the upgrade key.

In fact, SetupStore.php has been run on container startup, and only then php-fpm started. There is no cron in the container.

Is this so, and how can this be switched off? Updating the database without being explicitly told to do that is definitely wrong.

We're testing out SMW 4.1.3 on MW 1.39.8 and have noticed the following new behavior from the old MW 1.34.4, SMW 3.2.3 system we are not used to:

1. NULL EDITS no longer work as expected - it used to be we could trigger a SMW page property update on a page by opening the page up for source editing, adding a single white space anywhere on the page, and then clicking save.. the result we're used to is that MW does not register the added whitespace as an edit but the process causes SMW to update all properties calculated from other SMW queries ---- in the new wiki (SMW 4.1.3 on MW 1.39.8) the NULL edit does not force any SMW property updates

2. PF AUTOEDIT with "|reload" option reloads the page before SMW updates the data that was changed .. causing users to think the autoedit did not do anything.. it takes a second manual refresh of the page to see the the autoedit was successful.

Does anyone have any insight regarding this kind of issue/behavior when upgrading from an old version of SMW to something new?

We're testing out SMW 4.1.3 on MW 1.39.8 and have noticed the following change in behavior from the old MW 1.34.4, SMW 3.2.3 system that we are used to:

1. NULL EDITS no longer work as expected - it used to be we could trigger a SMW page property update on a page by opening the page up for source editing, adding a single white space anywhere on the page, and then clicking save.. the result we're used to is that MW does not register the added whitespace as an edit but the process causes SMW to update all properties calculated from other SMW queries ---- in the new wiki (SMW 4.1.3 on MW 1.39.8) the NULL edit does not force any SMW property updates
2. PF AUTOEDIT with "|reload" option reloads the page before SMW updates the data that was changed .. causing users to think the autoedit did not do anything.. it takes a second manual refresh of the page to see the the autoedit was successful.

Does anyone have any insight regarding this kind of issue/behavior when upgrading from an old version of SMW to something new?

We're testing out SMW 4.1.3 on MW 1.39.8 and have noticed the following change in behavior from the old MW 1.34.4, SMW 3.2.3 system that we are used to:

1. NULL EDITS no longer work as expected - it used to be we could trigger a SMW page property update on a page by opening the page up for source editing, adding a single white space anywhere on the page, and then clicking save.. the result we're used to is that MW does not register the added whitespace as an edit but the process causes SMW to update all properties calculated from other SMW queries ---- in the new wiki (SMW 4.1.3 on MW 1.39.8) the NULL edit does not force any SMW property updates
2. PF AUTOEDIT with "|reload" option reloads the page before SMW updates the data that was changed .. causing users to think the autoedit did not do anything.. it takes a second manual refresh of the page to see the the autoedit was successful.

The following cache settings are the same on both the old and new sites:

• $wgMainCacheType = CACHE_MEMCACHED;
• $wgParserCacheType = CACHE_NONE;
• $wgMessageCacheType = CACHE_MEMCACHED;

Does anyone have any insight regarding this kind of issue/behavior when upgrading from an old version of SMW to something new?