Opened 11 years ago
Last modified 8 years ago
#22995 new Cleanup/optimization
Deprecate auto_now and auto_now_add and document alternatives — at Initial Version
| Reported by: | Jannis Leidel | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | cmawebsite@…, someuniquename@… | Triage Stage: | Someday/Maybe |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
We've previously documented some side issues of the two options (e.g. #6434) but need to better clarify the downsides of those magic parameters. The ability to override the save method as well as the default parameter has long made this implicit feature capable of being replaced.
This would probably also be a way to not let users fall in the trap as documented in #16745 and #22571.
In a previous *old* discussion there were multiple core developers in favor of the deprecation: https://groups.google.com/forum/#!topic/django-developers/TNYxwiXLTlI
Note:
See TracTickets
for help on using tickets.