Nick ODell

I had the same problem. After tracing through Django Q, I found that this problem is caused by using the default caching settings. When that happens, this line in the...

The ORM broker is the slowest broker (in that it needs to repeatedly poll the database to find new work) and the least robust (in that exactly-once delivery is not...

>As I said, there are so many services (e.g. postgresql, Influxdb, etc.) had to deploy in this project. This begs two questions: 1. Why are you using both SQLite and...

>The official document doesn't record that Postgresql can be as the broker, does it ? The Django documentation says that [PostgreSQL can be used as a database backend](https://docs.djangoproject.com/en/3.2/ref/databases/#postgresql-notes). The Django...

Hard to say. There may be something misconfigured. Without going into each setting and checking it, it's hard to say. I've written a tutorial on how to set up django-q...

@Nicksia It's worth noting that while tasks are sent to the queue to dispatch them to a Django Q server, the broker is *not* involved in sending the task back...

@mkmoisen > Would you please elaborate a bit on what you mean by a difficulty in achieving exactly-once delivery with Django ORM, and the hacks necessary to accomplish it? I...

>One question about the 60 seconds default: What happens if you want to run one particular task that might take 10 minutes, but you also want to run normal tasks...

>Could you please tell me if we can have any indexes in the table django_q_schedule? I don't believe so, other than an index on the primary key. Here's what SHOW...

I don't think this is intended behavior. Reading `django_q/cluster.py`, here is how it handles exceptions in the task pusher: ```py try: task = SignedPackage.loads(task[1]) except (TypeError, BadSignature) as e: logger.error(e,...