#24198: Options.get_field behavior change
-------------------------------------+-------------------------------------
Reporter: xordoquy | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by pirosb3):
Replying to [comment:3 xordoquy]:
> Thanks Tim. I'm sorry I totally missed the migration guide.
Hi,
As Tim confirmed, the new Meta API allows GenericForeignKeys too. If you
are concerned this can be an issue on your side, you can easily filter it
our using the field flags. It should be the only field that has a '''one-
to-many''' cardinality without a specific '''related_model''' set.
As stated in the guide, '''related_model''' can be None if the relation is
generic.
Please feel free to contact me on IRC for any issues.
Dan
--
Ticket URL: <https://code.djangoproject.com/ticket/24198#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.ed324bdacc43d95d0d0aa8dc78f32bbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
