#24289: Is usage of many_to_one and one_to_many terms confusing for relation
flags?
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Release blocker | Resolution:
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 collinanderson):
Using something like "remote_many" is also fine with me.
One thing we many need to do it try going through the codebase and
changing some isinstance() check to use these flags. I know the admin for
example, needs to be able to predict how things will cascade when deleting
an object, which a "field.one_to_one" flag is not a good enough on its own
for that.
--
Ticket URL: <https://code.djangoproject.com/ticket/24289#comment:15>
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.a75e3ea8ac42d63254c6f676a23fccb7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
