Summary Re: Migrations: A bug or a feature needing documentation?

2019-08-08 Thread Barry Johnson
On Monday, August 5, 2019 at 4:55:24 PM UTC-5, Barry Johnson wrote: > > [ TL;DR: A migration may use a “replaces” list pointing to migrations that > don’t actually exist. This undocumented technique cleanly solves a > recurring difficult migration problem. We seek consensus on whether this

Re: Migrations: A bug or a feature needing documentation?

2019-08-08 Thread Barry Johnson
On Wednesday, August 7, 2019 at 9:22:27 PM UTC-5, Markus Holtermann wrote: > > Let's look at the last question first, regarding duplicate entries in the > django_migrations table: Yes, this is to be a bug. At least how it's > currently used. > Agreed. > Let's say you have migration

Re: Migrations: A bug or a feature needing documentation?

2019-08-08 Thread Barry Johnson
On Wednesday, August 7, 2019 at 2:17:45 PM UTC-5, Adam Johnson wrote: > > Some questions: Have you looked into the migration framework internals? > Are there any comments around "replaces" that indicate this behaviour? And > is there maybe a way of hooking into the migration planner, or adding

Re: Migrations: A bug or a feature needing documentation?

2019-08-07 Thread Markus Holtermann
Hi Barry, TL;DR: I think this is a bug and can lead to inconsistencies in other project setups than yours. Let's look at the last question first, regarding duplicate entries in the django_migrations table: Yes, this is to be a bug. At least how it's currently used. Let's say you have

Re: Migrations: A bug or a feature needing documentation?

2019-08-07 Thread Adam Johnson
Hi Barry, I don't have a very strong opinion here, but replying with some questions, and to bump the thread. I think this smells more like a bug than a feature to me. I worry that if you depend on it, it could easily get refactored away in a future version of Django. If we were to document it

Migrations: A bug or a feature needing documentation?

2019-08-05 Thread Johnson, Barry
[ TL;DR: A migration may use a “replaces” list pointing to migrations that don’t actually exist. This undocumented technique cleanly solves a recurring difficult migration problem. We seek consensus on whether this should become a documented feature or that it is an unexpected side effect