https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27783
--- Comment #36 from Tomás Cohen Arazi <[email protected]> --- (In reply to Jonathan Druart from comment #30) > 1. Shouldn't we force the job to define its queue? Otherwise I have the > feeling that we will end up with "default" everywhere. I've been trying to think of use cases, and the authority merge came to my mind. If the record count is low enough it would be great to do it real-time (because librarians really want to keep working on those records, probably), and if it is too big, it would be great to do it in the long_tasks queue (because it wouldn't need to wait for the cronjob). So, in this case, ->enqueue could actually put the job in different queues depending on the scenario. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
