#23808: manage.py runserver creates django_migrations without concent
--------------------------------+--------------------
Reporter: jorgecarleitao | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------
When you run `./manage.py runserver` on a database without
`django_migrations` table, the command issues a `CREATE` to create the
table.
While this seems natural for users trying to run the server the first
time, I would not expect a database interaction (specially a `CREATE`
statement) from a `runserver`. The user is not being informed that the
database is being changed.
At least, this should be mentioned in the documentation, but IMO it is odd
that a `runserver` is issuing `CREATE` statements.
Of course, this is a consequence of not running `manage.py migrate`
before.
--
Ticket URL: <https://code.djangoproject.com/ticket/23808>
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/057.9b0a9509cf94ca114dcfabfcb035c67d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
