#15045 closed (fixed)
auto_now_add is also referred to as auto_add_now
Reported by: | Jacco | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.2 |
Severity: | Keywords: | auto_now_add, auto_add_now | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The note near DateField.auto_now_add (http://docs.djangoproject.com/en/dev/ref/models/fields/#datefield)currently states (emphasis added):
As currently implemented, setting auto_now or auto_add_now to True will cause the field to have editable=False and blank=True set.
Shouldn't this be changed into auto_now_add?
Change History (3)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Ready for checkin |
---|
comment:2 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 14 years ago
Note:
See TracTickets
for help on using tickets.
(In [15171]) Fixed #15045 - Typo auto_add_now -> auto_now_add; thanks dr_gone for the report.