Closed shutupflanders closed 1 year ago
Hey @shutupflanders - thanks a lot for your contribution! This looks like a great idea - definitely useful.
What do you think of using --all
or --purge
instead of --force
? --force
makes me think of removing migrations in production, where the action is usually protected. I think --all
or --purge
better describe the fact it's removing everything job-status related from the database?
--all
sounds like the best option!
--force
option tojob-status:clear
commandI was unable to "start again" after stopping jobs midway / clearing my queuing system, and had leftover artefacts in the database.
This will ignore all the constraints when searching for job data to prune and remove everything.
Hopefully this is useful to others!