Sunday, July 27, 2014

Why are DateTimeField auto_now and auto_now_add bad?

Hi all,

I've seen DateTimeField's auto_now and auto_now_add parameters often described as "buggy" or "error-prone". For example:
https://code.djangoproject.com/ticket/22995
https://groups.google.com/forum/#!topic/django-developers/TNYxwiXLTlI

The ticket proposes to document these downsides or problems in more detail. But until that happens, is there a blog post or mailing list post somewhere that summarises the gotchas to watch out for with auto_now?

Thanks,

Mattias

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9d61eca2-21c7-41ae-a921-a448d5f9f4f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment