Opened 15 years ago
Last modified 14 years ago
#12938 new
not possible to validate a many-to-many at the model — at Version 1
| Reported by: | ryazwinski | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 |
| Severity: | Normal | Keywords: | many_to_many, validation |
| Cc: | contact@… | 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 )
Reference ticket #12065 for genesis of this ticket.
It isn't currently possible to perform model-level validation of many-to-many relationships.
For example:
class Test(models.Model):
f1 = models.CharField(max_length=100)
m2m = models.ManyToManyField(Other)
It is not possible to ensure that the f1/m2m relationship is unique. Validation in the Test class cannot validate the m2m because Test won't have been saved yet.
Change History (1)
comment:1 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
Note:
See TracTickets
for help on using tickets.
Accepted, but this isn't going to be easy to fix, due to the somewhat disconnected relationship between m2m tables and their parent models.