#17654: auto_now_add=True column creates IntegrityError if model is saved by
specifying an id
-------------------------------------+-------------------------------------
Reporter: gtorok@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Keywords: auto_now_add,
Severity: Normal | IntegrityError
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
To reproduce, create a new model which has an auto_now_add=True field and
specify the id. When calling save() the IntegrityError is raised:
# Order has this field: created_at =
models.DateTimeField(auto_now_add=True, null=False)
o = models.Order(id=1, name="abc")
o.save()
IntegrityError: null value in column "created_at" violates not-null
constraint
--
Ticket URL: <https://code.djangoproject.com/ticket/17654>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
