#15953: Allow setting individual fields as 'unique' from the model Meta options
-------------------------------------+-------------------------------------
Reporter: julien | Owner: nobody
Type: New | Status: new
feature | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by Alex):
* stage: Unreviewed => Design decision needed
Comment:
I'm -1 on this feature, it moves a field level option to the model level,
which is wrong, also if the issue is inheritance solving just one special
case is the complete wrong way to do this. Finally, a strong argument can
be made that it's completely inappropriate to allow changing the field on
subclasses (even in the abstract case, it obviously is in the MTI case).
Marking as DDN for now, but I'm inclined to wontfix it.
--
Ticket URL: <http://code.djangoproject.com/ticket/15953#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
