#16286: Models virtual fields and ModelForms
-------------------------------------+-------------------------------------
Reporter: loic84 | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) |
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
-------------------------------------+-------------------------------------
Comment (by jpic):
> Currently the only virtual field in Django is GenericForeignKey and it
doesn't need this feature because each local field it relies on is
responsible for its own data.
How can the object_id field be validated without the knowledge of its
GFK's content_type field ?
I'd like to re-open this: some apps have been providing working widgets
for GFK for years now, so there's got to be a way.
--
Ticket URL: <https://code.djangoproject.com/ticket/16286#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/064.bd09298d1def5a600008c3ccc3abc38c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
