Opened 6 years ago

Last modified 5 years ago

#12938 new New feature

not possible to validate a many-to-many at the model

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 russellm)

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 (7)

comment:1 Changed 6 years ago by russellm

  • Description modified (diff)
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

Accepted, but this isn't going to be easy to fix, due to the somewhat disconnected relationship between m2m tables and their parent models.

comment:2 Changed 6 years ago by jkocherhans

Just for the logs, Honza and I asked Rick to file this after a discussion about a bug flatpages. We're aware that it's going to be reaaaaaaly hard. :(

comment:3 Changed 5 years ago by anonymous

  • Cc contact@… added

comment:4 Changed 5 years ago by lukeplant

  • Type set to New feature

comment:5 Changed 5 years ago by lukeplant

  • Severity set to Normal

comment:6 Changed 4 years ago by aaugustin

  • UI/UX unset

Change UI/UX from NULL to False.

comment:7 Changed 4 years ago by aaugustin

  • Easy pickings unset

Change Easy pickings from NULL to False.

Note: See TracTickets for help on using tickets.
Back to Top