Opened 18 years ago

Closed 18 years ago

Last modified 17 years ago

#1260 closed defect (invalid)

can't use DateTimeField with auto_now

Reported by: anykey@… Owned by: Adrian Holovaty
Component: contrib.admin Version: dev
Severity: normal Keywords: __repr__ DateTimeField auto_now
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


mod_python shows an not very helpful error if a model uses a DateTimeField with auto_now=True which makes it a bit cumbersome to navigate in admin interface. It seems this is raised by the template which says "BlaBla was successfully created. ..." on the top f the page after creating a object and clicking on any of the save buttons.

I would say, at this moment the datetime value is not yet set, which causes this error, but this is only a guess.

Change History (2)

comment:1 Changed 18 years ago by Adrian Holovaty

Resolution: invalid
Status: newclosed

Please reopen if this is still a problem.

comment:2 Changed 17 years ago by URL

Summary: can't use DateTimeField with auto_now=True together with __repr__can't use DateTimeField with auto_now
Note: See TracTickets for help on using tickets.
Back to Top