Opened 19 years ago
Closed 17 years ago
#1056 closed defect (fixed)
auto_now_add=True broken with ChangeManipulator
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | contrib.admin | Version: | |
Severity: | major | Keywords: | |
Cc: | gomo@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
This is from the current DateField definition (django/core/meta/fields.py):
def pre_save(self, value, add): if self.auto_now or (self.auto_now_add and add): return datetime.datetime.now() return value
When you modify an object that has this field using it's ChangeManipulator, the field gets set to "null" from the request, because the DateTime fields with auto_now_add=True or auto_now=True are not editable (line 387 of the same file).
An additional elif clause should be added to catch this problem, like this:
def pre_save(self, value, add): if self.auto_now or (self.auto_now_add and add): return datetime.datetime.now() elif self.auto_now_add: return the_current_value_from_the_db else: return value
I'm posting the ticket instead of a patch because I'm not sure how to get the current value from the DB from the field instance.
Change History (4)
comment:1 by , 19 years ago
milestone: | → Version 1.0 |
---|
comment:3 by , 18 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:4 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Correct me if I am wrong, but since the removal of auto_now_add this isn't a problem in trunk. Reopen if I am incorrect.
This will likely become moot since auto_now_add should go away...