Opened 16 years ago
Last modified 14 years ago
#8334 closed
Allow add/create on m2m intermediate tables if all the non-FK fields have defaults or are NULLable — at Version 2
| Reported by: | Gergely Kontra | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | manytomany through default add create |
| Cc: | ales.zoulek@… | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Add/create is currently disabled on m2m relations that use an intermediate table. This is due to the fact that values to populate the intermediate table cannot be provided using the add/create calls.
However, what if the intermediate model has reasonable default values, so
one can assign model A to B without extra info?
In my case, I just want to syncronize 2 databases, and I would like to
mark relationships, that are already synced. So, in my case, the
intermediate table contains a boolean, which defaults to false, and
will become true, when the data is synced.
In this case adding relations without explicitly creating the intermediate table would be great.
(based on this thread in the ML)
Change History (2)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 16 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Allow add/create if all the non-FK fields have defaults or are NULLable → Allow add/create on m2m intermediate tables if all the non-FK fields have defaults or are NULLable |
Updated description and summary to describe the problem better.
Marking as accepted because it makes sense.