Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A job with a db exception is never handled (moved to failed) by the worker #8

Open
bretth opened this issue Dec 9, 2013 · 0 comments

Comments

@bretth
Copy link
Owner

bretth commented Dec 9, 2013

Because workers share the Django db stack they are vulnerable to exceptions in jobs. Essentially the design would be better all round if django-pq used it's own connection handlers which aren't shared with jobs. This would also make it easier to receive notification of new jobs via the postgres connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant