View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|16483||Bug reports||Conditions||public||2020-07-10 13:22||2020-08-03 12:54|
|Summary||16483: Adding condition triggers bulk update for complete database|
When adding a condition to a question (no matter which type, values or scenario), the complete database is processed, instead of just processing the survey you were working in.
NULL is passed as a first argument instead of the active survey ID to LimeExpressionManager::UpgradeConditionsToRelevance(null, $qid);
This makes it so that every time a condition is added, the complete database is processed. In the case of my client, this is a very large database with many surveys, questions and conditions. This then results in either PHP running out of memory, or the server timing out and throwing an error.
|Steps To Reproduce|
Do note that the condition actually gets added correctly. It is the next action (LimeExpressionManager::UpgradeConditionsToRelevance) that causes the timeout/crash.
|Complete LimeSurvey version number (& build)||4.2.5|
|I will donate to the project if issue is resolved||No|
|Database & DB-Version||MySQL 10.3.22 (MariaDB)|
|Server OS (if known)||Ubuntu 20.04 LTS|
|Webserver software & version (if known)||Apache/2.4.41 (Ubuntu)|