Jake Howard

I think "I want to keep task results for a long time" is an anti-pattern. The result should be short-lived, and persisted to somewhere else (ie your business logic) in...

That sounds like the ideal start to me. I'm not sure what the query plan would look like for combined indexes vs separate ones, but it's hard to know that...

This is fantastic! An index on `status` makes sense, since most of the time that's going to cut down the number of rows quite a lot. `queue_name` ought to help...

Yes that does sound sensible. I'd definitely welcome a PR to fix it. You've put it your index one but the fix should be separate.

@eviljeff Looked further into this, the current functionality is exactly how you describe - ascending will give the oldest date first, which is correct and how it's implemented now.

Having a limit, after which tasks can be picked up again seems to be the standard way forward - it's what many other queue libraries do. I'm currently looking to...

Yes, there are plenty. If the process shuts down cleanly, it's handled. If the server suddenly drops off (eg power or network issue), or a less-clean exit (eg segfault).

You are, an absolute legend! > Should it be possible to run the worker via a management command I think deferring to however Celery runs its tasks even without `django-tasks`...

My main thinking is around people wanting to slowly use `django-tasks`, without needing to rewrite all their Celery integration. If `django-tasks` defines the app, people can't use their own. Is...

> I'm not sure if cloning is IO-bound or CPU-bound I think cloning is more IO-bound, since really it's just copying data between DBs (rather than doing much transformation in...