#32217: Add warning about missing 'migrations' package to migration docs
------------------------------------------------+--------------------------
Reporter: Tim McCurrach | Owner: nobody
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: 3.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+--------------------------
If you create an app with no migrations folder, then running
`makemigrations` won't make migrations for that app. This isn't really
mentioned in the migrations doc. There is a section dedicated to apps
where the database is already set up and migrations are missing, but
someone who has simply created an app manually might gloss over that
section. The only place I could actually find this written down is in a
comment in `db.migrations.questioner` (lines 26-33).
I have been bitten by this a few times, and only noticed my migrations
weren't added until further on down the line when I get a database error.
I think it would be helpful to have the above explicitly stated in the
docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/32217>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.ae9850d33e1cf8549df244691415d2e2%40djangoproject.com.
