altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity

Make sure MilestoneHistory doesn't have an auto_now on the time field

Browse source 
- Legacy-Id: 4580
This commit is contained in:
Ole Laursen 2012-07-03 23:25:49 +00:00
parent 317c0ce683
commit 1d0ba6c341
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
ietf/group/models.py
View file

@ -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):