#11403: Django Models - Default and Choices made to Table Schema
-------------------------------------+-------------------------------------
Reporter: seanmccully | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.0
(models, ORM) | Resolution: needsinfo
Severity: Normal | Triage Stage: Design
Keywords: Models Default | decision needed
Choices | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => needsinfo
Comment:
This ticket is really about two different features:
1) storing default in the database
2) using enum fields for fields with a limited number of choices
The main drawback both ideas is that changes to the default value or
choices will have to be propagated to the database. This requires schema
alteration.
These are large problems, I suggest sending concrete proposals to django-
developers. The proposal should address backwards-compatibility and if
possible include a proof of concept.
--
Ticket URL: <https://code.djangoproject.com/ticket/11403#comment:5>
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].
For more options, visit https://groups.google.com/groups/opt_out.
