#33829 closed Bug (fixed)
BaseConstraint.deconstruct() and __eq__ operators don't take violation_error_message into account.
Reported by: | Mariusz Felisiak | Owned by: | Stéphane "Twidi" Angel |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 4.1 |
Severity: | Release blocker | Keywords: | |
Cc: | Gagaro | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Thanks Stéphane "Twidi" Angel for the report.
Regression in 667105877e6723c6985399803a364848891513cc.
Change History (8)
comment:1 by , 2 years ago
Has patch: | set |
---|
comment:2 by , 2 years ago
Summary: | BaseConstraint.deconstruct() doesn't take violation_error_message into account. → BaseConstraint.deconstruct() and __eq__ operators don't take violation_error_message into account. |
---|
comment:3 by , 2 years ago
Needs tests: | set |
---|---|
Patch needs improvement: | set |
comment:5 by , 2 years ago
Needs tests: | unset |
---|---|
Patch needs improvement: | unset |
Triage Stage: | Accepted → Ready for checkin |
Note:
See TracTickets
for help on using tickets.
PR