#26304: Unable to use unmanaged ManyToMany through models when backed by a View.
-------------------------------------+-------------------------------------
Reporter: schinckel | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by schinckel):
Replying to [comment:3 MarkusH]:
> > I believe that this can be resolved by only adding those many-to-many
fields that do not have a through model marked as unmanaged.
>
> Don't you run into an issue if the rows on either end of the M2M field
are truncated but the rows in the through table still exist pointing to
nowhere, which effectively would blow up with broken foreignkey
constraints?
In my case, it is a View that is acting as the model source: which cannot
_ever_ be truncated.
--
Ticket URL: <https://code.djangoproject.com/ticket/26304#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.b4ba00ed91331266169ebc8b29b270a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
