#23932: models.UUIDField() documentation / migrations
--------------------------------------+------------------------------------
Reporter: michaeljohnbarr | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
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 michaeljohnbarr):
Excellent points. Another talking point that may be helpful is how one
might handle inheritance with migrations (such as creating a base
migration). Assuming we have an abstract model that can be extended, what
would be the suggested standard to handle the migration for new/existing
models? It is difficult to know which fields already exist on the models,
and which fields don't. Thus, it appears that each migration for each app
would have to be hand-coded.
Thank you for your consideration, responses, and clarification.
--
Ticket URL: <https://code.djangoproject.com/ticket/23932#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.f5cbefb7a078aad9f0f3bedef8554d60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
