saxix/django-concurrency — pull request #42 by Naddiseo (2014-10-10 05:05:03+00:00)
Title: Failing testcase for issue #41

Here's a currently failing testcase for the problem I mentioned in PU #41.
The steps I took to create it:

1. Create a new model with a `db_table` set to "issue41"
1. Create a new migration
1. Remove the `db_table` option.
1. Manually create a new migration that renames the table.

Django-concurrency fails when running the first of the two migrations because it looks for `db_table` under the current model. I had a look into it over the past hour, but I haven't been able to come up with a clean way to get it working. I think a big part of the problem is that django doesn't pass the signal handler the migration's view of the models, and instead passes the current model. I'm not sure how to get around it. My current work around in my work project is to just disable the `post_syncdb_concurrency_handler` altogether and create the triggers via the management command.