Admin integration is broken when using ORM as a broker with a different database

Hello,

I’m using ORM as a broker and I have exactly followed the same steps mentioned at the docs regarding using a separate DB for django_q and applying migrations.

However, when browsing admin dashboard I always get relation "django_q_schedule" does not exist when trying to open anything under DJANGO_Q section except for Queued tasks, this was clearly about that it doesn’t use the correct DB, so I looked at admin.py and my guess was right, using() connection is only respected with QueueAdmin and others are not at all, I have even tried to add using() for TaskAdmin and it worked as expected, so it is all about that.

I’m using Django 2.2.16 and PostgreSQL 12.3

[pfgoting]

Hello! Sorry for resurrecting this old thread since I just encountered the same issue as the original poster. So if my understanding is correct, when using another database as a broker, all task-related data except Queued tasks are still saved on the default database. Therefore, 2 migrations need to be run. The first migration is to have django_q_schedule and django_q_task on your default DB, while the second would be for django_q_ormq on your broker database.

I think this was designed such that even when changing brokers, the task data would remain intact on only one database. Think of a scenario wherein you started using another DB as a broker but then switched to Redis. This would result in you still keeping the separate broker database even though it outlived its main purpose already.

[Koed00]

Good spot. Seems like an easy enough fix.