Alex Ball
Alex Ball
@chrisspen I believe this now fully addresses the problem you reported in #457. I think the root cause of that problem lies more with the index collision than with migration...
Yeah, after further testing last night I'm not 100% sure this is a you problem... might be an us problem, since I was unable to reproduce it with a *new*...
`sqlmigrate` output for the relevant schedule migrations, 0001 and 0008, on Postgres: (note how `schedule_calendar_slug_ba17e861_like` is created twice) ``` m sqlmigrate schedule 0001 Loaded settings for site "mysite" in role...
Postgres 11.5, psycopg2 2.8.3, django 2.2.6, django-scheduler 0.9.2 Will try again from master and continue investigating.
Okay, at this point I suppose I'll have to settle for overriding migrations in our project (`MIGRATION_MODULES`). Feel free to close this if you can't reproduce it :/