Django DateTimeField auto_now_add not working

2019-03-15 12:36发布

In one of the model i have set one timestamp field as follows:

created_datetime = models.DateTimeField(auto_now_add = True)

While in shell i am able to create a obj and save it, however in my application it is raising a exception that created_datetime field cannot be null.

Confused where things went wrong!! How to reslove it.

4条回答
虎瘦雄心在
2楼-- · 2019-03-15 12:57

I had this and it really confused me for ages.

Turned out that my model had a custom primary key, and it was due to a bug not setting it when constructing some test objects.

The first time this worked fine as auto_now_add set created_at. The second time it didn't as the object with a null primary key already existed, so it was doing an update. And it tried to set that to created_at null, which wasn't allowed in my model.

So worth checking if you end up on this question with the error "in my application it is raising a exception that created_datetime field cannot be null", that that could be caused by not setting a primary key correctly.

The solution was for me to correctly set a primary key.

查看更多
迷人小祖宗
3楼-- · 2019-03-15 13:01

You can do something like this

created_datetime = models.DateTimeField(auto_now_add=True, auto_now=False)
查看更多
做个烂人
4楼-- · 2019-03-15 13:05

As far as I know, best practice for default datetimes is to use the following:

created_datetime = models.DateTimeField(default=datetime.datetime.now)

Don't forget to import datetime

查看更多
一纸荒年 Trace。
5楼-- · 2019-03-15 13:06

The following way is in the "part1" of django documentation

from django.utils import timezone
p = Poll(question="What's new?", pub_date=timezone.now())
查看更多
登录 后发表回答