Opened 4 weeks ago
Last modified 3 weeks ago
#35358 new Cleanup/optimization
Rename BaseConstraint._check() to check()
Reported by: | Simon Charette | Owned by: | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | 6.0 |
Cc: | Mariusz Felisiak | Triage Stage: | Someday/Maybe |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Per this comment , BaseConstraint._check()
should be renamed to check()
in Django 6.0 when the deprecation period for BaseConstraint.check
(now .condition
) ends.
Change History (2)
comment:1 by , 4 weeks ago
Description: | modified (diff) |
---|---|
Keywords: | 6.0 added |
Summary: | Rename BaseConstraint._check to check once the deprecation period → Rename BaseConstraint._check() to check() |
Triage Stage: | Unreviewed → Someday/Maybe |
comment:5 by , 3 weeks ago
To make it clear, this ticket cannot be worked on until Django 6.0 which will remove the deprecation shim for CheckConstraint.check
in favor of .condition
which will allow BaseConstraint.check
to be reclaimed.
Note:
See TracTickets
for help on using tickets.
For past releases, I put the Django version number in the keywords field and used that Trac query (example).