From 9ef8a4371eeee4c9f3d6b3f008fc9af00bd333f3 Mon Sep 17 00:00:00 2001 From: Andreas Zweili Date: Thu, 4 Jan 2018 12:30:01 +0100 Subject: [PATCH] correct the datetimefield on the orders model In Django it's better to use timezone.now instead of datetime.now() this is because it has additional settings for timezones which this way wouldn't get reflected in the attributes and lead to wrong datetime values. --- django/didgeridoo/webshop/models.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/django/didgeridoo/webshop/models.py b/django/didgeridoo/webshop/models.py index ecb6678..3bb3442 100644 --- a/django/didgeridoo/webshop/models.py +++ b/django/didgeridoo/webshop/models.py @@ -2,7 +2,7 @@ from decimal import Decimal from django.core.validators import MinValueValidator from django.db import models from django.contrib.auth.models import User -import datetime +from django.utils import timezone class Option(models.Model): @@ -86,7 +86,7 @@ class Order(models.Model): user = models.ForeignKey(User, on_delete=models.CASCADE) article = models.ManyToManyField(Article, through='OrderPosition') status = models.ForeignKey(OrderStatus) - date = models.DateTimeField(default=datetime.datetime.now()) + date = models.DateTimeField(default=timezone.now) class OrderPosition(models.Model):