as described in the issue #652
django-q queries a lot for tasks and schedules.
to keep django-q on a different db, preferably on a no-sql db
while the main app in on a sql db and still use a different broker like redis.
the solution prevents transaction lock on different databases by using the db-route.
as described in the issue #652 django-q queries a lot for tasks and schedules. to keep django-q on a different db, preferably on a no-sql db while the main app in on a sql db and still use a different broker like redis.
the solution prevents transaction lock on different databases by using the db-route.