#16286: Models virtual fields and ModelForms
-------------------------------------+-------------------------------------
Reporter: loic84 | Owner: nobody
Type: New | Status: closed
feature | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: invalid | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by ptone):
* status: new => closed
* resolution: => invalid
Comment:
There is no practical way to do this in a general purpose way in Django -
no way for Django to know which widget to use. This is a case where the
solution is to subclass ModelForm and add the form field and behavior you
expect for your custom model implementation.
RE the other comment, I believe the OP was not talking about composite PK,
but more the use of get/set methods exposed as a property on a model.
--
Ticket URL: <https://code.djangoproject.com/ticket/16286#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
