From 1d0ba6c3419d8653b5e7d7b1d1d263638cd85fa9 Mon Sep 17 00:00:00 2001 From: Ole Laursen Date: Tue, 3 Jul 2012 23:25:49 +0000 Subject: [PATCH] Make sure MilestoneHistory doesn't have an auto_now on the time field - Legacy-Id: 4580 --- ietf/group/models.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ietf/group/models.py b/ietf/group/models.py index 0283dbd0c..169497387 100644 --- a/ietf/group/models.py +++ b/ietf/group/models.py @@ -70,7 +70,6 @@ class GroupMilestoneInfo(models.Model): desc = models.CharField(verbose_name="Description", max_length=500) due = models.DateField() resolved = models.CharField(max_length=50, blank=True, help_text="Explanation of why milestone is resolved (usually \"Done\"), or empty if still due") - time = models.DateTimeField(auto_now=True) docs = models.ManyToManyField('doc.Document', blank=True) @@ -81,9 +80,10 @@ class GroupMilestoneInfo(models.Model): ordering = ['due', 'id'] class GroupMilestone(GroupMilestoneInfo): - pass + time = models.DateTimeField(auto_now=True) class GroupMilestoneHistory(GroupMilestoneInfo): + time = models.DateTimeField() milestone = models.ForeignKey(GroupMilestone, related_name="history_set") class GroupStateTransitions(models.Model):