#22571: Document implications of using auto_now_add=True and get_or_create
-------------------------------------+-------------------------------------
Reporter: nu.everest@… | Owner: yamila-
Type: | moreno
Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.4
Severity: Normal | Resolution: fixed
Keywords: integrityerror | Triage Stage: Accepted
auto_now_add get_or_create |
duplicatekey |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"cbe4efcbc13ad402bf1f1a94b02a8ec93f20327d" cbe4efc]:
{{{
#!CommitTicketReference repository=""
revision="cbe4efcbc13ad402bf1f1a94b02a8ec93f20327d"
Fixed #22571 -- Added clarification about auto_now_add=True
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22571#comment:9>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/078.cd28562bd0a93e962f86325899fb6b36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
