Remove django_workable.

[glogiotatidis]

We never actually used workable and now we're moving to another provider.

So @jgmize, @pmclanahan how do you feel about removing django_workable database tables using a migration from the base app? (commit 1086317) Do you think its worth it or should I just go and manually run those commands?

[jgmize]

Do you think its worth it or should I just go and manually run those commands?

Personally, I'd run them manually after the code has been deployed. Given that there are no other migrations, it's not worth adding them just for this case. Also, there's a potential race condition where if the migrate command was run as part of a deploy and dropped the tables, the other deployed containers running the previous version of the code talking to the same DB could potentially throw errors. There is also the fact that there's no automatic rollback option as implemented here, and no real downside if you left the unused tables in the DB for a while and dropped them only after there was no possibility of ever needing to roll back to a version of the code that included references to those tables.

[glogiotatidis]

All good points jgmize. I'll remove the migrations and apply them manually. Thanks!