Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#21375 closed Bug (fixed)

Related_name='+' shouldn't clash with another '+'

Reported by: Anssi Kääriäinen Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

A relation (fk or m2m) that defines its related name as '+' shouldn't cause a model validation error if there is another relation for the same model with '+'.

Change History (2)

comment:1 by Anssi Kääriäinen <akaariai@…>, 10 years ago

Resolution: → fixed
Status: new → closed

In 9f76ea1eaad0db0183fa3b5bade16392db0cafbd:

Fixed #21375 -- related_name='+' clashed with other '+' names

comment:2 by Loic Bistuer <loic.bistuer@…>, 10 years ago

In 82a58ce5b67e0b79fa0efbad72e21d9d1be25ceb:

Fixed #21491 -- Removed documented workaround for a known issue.

The issue was that two M2M hidden reverse managers
(related_name ending with a '+') could clash with each other.

Refs #21375 and #15932. Thanks Baptiste.

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