#28004: Document how to add migrations to an app
--------------------------------------+------------------------------------
Reporter: René Fleschenberg | Owner: rene@…
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: docs migrations | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by René Fleschenberg):
Tim, thank you for your super-quick reaction!
I now found https://docs.djangoproject.com/en/1.10/topics/migrations
/#adding-migrations-to-apps, which is where I should have pointed the user
at. So this is in fact properly documented already. My bad for not looking
harder, sorry.
On the other hand, papna is (I think) an experienced Python user, so one
could argue that we have a discoverability problem here.
I wonder if we should change the behaviour of `makemigrations` to write
migration files even for apps that don't have a `migrations` package. This
would be less surprising, I think.
In any case, I think this issue is of fairly low priority.
--
Ticket URL: <https://code.djangoproject.com/ticket/28004#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.6ebac9338d21a51fdb5b81daae1ac97f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
