Stop getting preferred archive for some SQL queries when there's no archive tool
With complex security scripts to calculate user groups, calling getPreferredArchive() from DA.__call__ still causes "maximum recursion depth exceeded" errors when caches are empty. In order to address the issue, we must review erp5_archive. Instead of that, this commit first checks whether the archive tool is installed, which is anyway faster that getting a preference. An expected failing test is also added.
Showing
-
Owner
+1
I think archives were never used besides when they were developped for baobab 10 years ago.
And yes, getPreferred* is way too expensive for such low-level tasks, sadly...
Please register or sign in to comment