Scheduler compatibility about moodle-tool_mergeusers HOT 1 OPEN

Hi!

Thanks for your words. There is a tracker in Moodle which motivates to include this plugin into core: https://tracker.moodle.org/browse/MDL-61542. You could post there, vote it, to try to push it a bit more. More votes, more possibilities to work on it by Moodle HQ.

However, I think that for including this functionality of merging users (instead of including this plugin as-is), this should be reworded into a new API, so that any part/component/plugin of Moodle defines how to do that. The default behaviour should be the current one: travel database table by table, but enabling that any part of Moodle define how to do that. There are so many issues and special cases related to specific behaviour of all these parts of Moodle (like grades, quiz attempts, and so many others). This approach would enable to adopt it progressively into Moodle core.

Regarding to your question: it would be very useful and convenient to process a single merge users into slots. I agree. The problem arised is how to define these slots: by amount of tables to work on? What should happen if a slot presents an error? Should the rest of slots be processed no matter previous errors if any or should it stop?

There is another issue created to convert any single merging into a single adhoc_task, so that cron.php would process it. However, a single merging could take half an hour easily on our instance, which have aournd 20K users in total. So the idea is go ahead a bit more, and analyse how to create several adhoc_tasks per merging.

Thanks for your words and vote that tracker and ask for voting it ;-)

Jordi

from moodle-tool_mergeusers.