Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#15045 closed (fixed)

auto_now_add is also referred to as auto_add_now

Reported by: dr_gone 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: UI/UX:

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 Changed 4 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Ready for checkin

comment:2 Changed 4 years ago by timo

  • Resolution set to fixed
  • Status changed from new to closed

(In [15171]) Fixed #15045 - Typo auto_add_now -> auto_now_add; thanks dr_gone for the report.

comment:3 Changed 4 years ago by timo

(In [15172]) [1.2.X] Fixed #15045 - Typo auto_add_now -> auto_now_add; thanks dr_gone for the report.

Backport of r15171 from trunk.

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