Skip to content Skip to sidebar Skip to footer

Why Does Django-lint Tell Me The `auto_now_add` Is Deprecated?

Hi fellow Djangonauts: I checked my project with django-lint, and it yields: W:211,16:MyModel: timestamp: Uses superceded auto_now or auto_now_add The commit message: auto_now/aut

Solution 1:

The correct fix is to pass a callable as the field's default that returns the appropriate datetime, e.g. datetime.datetime.now.

Solution 2:

auto_now and auto_now_add are considered harmful, because you have absolutely no way to change the value via django (say for example, in the admin interface).

This is an inconsitency with other flags, and django people generally don't like that sort of magic.

Post a Comment for "Why Does Django-lint Tell Me The `auto_now_add` Is Deprecated?"