#25453: makemigrations suggestion seems to go against best practices
--------------------------------------+------------------------------------
Reporter: piquadrat | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by piquadrat):
It's a bit of a temporal issue. At the point where it asks you, you should
already have created the data migration. How about
> Ignore for now, and let me handle existing rows with NULL myself (e.g.
because you added a RunPython or RunSQL operation to handle NULL values in
a previous data migration)
It's a bit longer, but it mentions "data migration", which is pretty
google-able for people that are a bit lost at this point.
--
Ticket URL: <https://code.djangoproject.com/ticket/25453#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/067.f2da6c45a293727b436ef8026920dcb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
