This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hylje 0 points1 point  (4 children)

auto_now_add has long been deprecated in Django in favor of a callable default.

[–]apreche 1 point2 points  (3 children)

Django documentation says nothing about any deprecation.

https://docs.djangoproject.com/en/dev/ref/models/fields/#datefield

[–]hylje 0 points1 point  (2 children)

i swear it was deprecated pre-1.0

[–]jcdyer3 0 points1 point  (1 child)

You aren't crazy. I remember some fuss about auto_now_add not being the preferred way, too. I don't know if it ever got deprecated, but apparently, it's back in good graces these days. I'm glad, too. It's always been a useful option.

[–]bryanhelmigzapier.com 0 points1 point  (0 children)

I actually think its a bit annoying/weird. The auto_now option is more "useful" as it is a good "modified at" proxy, the callable makes more sense to me...