#28347: Allow custom attributes for model fields
-------------------------------------+-------------------------------------
Reporter: Tom Turner | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => New feature
* component: Uncategorized => Database layer (models, ORM)
Comment:
What's the problem with writing a custom model field? My inclination is
that allowing a dictionary of arbitrary options isn't a good design as it
can be used and abused for any purpose and different Django applications
might choose conflicting key names for different purposes.
--
Ticket URL: <https://code.djangoproject.com/ticket/28347#comment:4>
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.aa1a696abf38780b3536e07e047b16b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
