#29706: RenameContentType._rename() doesn't save the content type on the correct
database
-------------------------------------+-------------------------------------
Reporter: Tyler Morgan | Owner: Hasan
| Ramezani
Type: Bug | Status: closed
Component: | Version: master
contrib.contenttypes |
Severity: Normal | Resolution: fixed
Keywords: RenameContentType | Triage Stage: Accepted
transaction atomic content_type |
update_fields using |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"661e6cc2c97d9bcb45198be787409488e1825c90" 661e6cc]:
{{{
#!CommitTicketReference repository=""
revision="661e6cc2c97d9bcb45198be787409488e1825c90"
Fixed #29706 -- Made RenameContentType._rename() save to the correct
database.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29706#comment:8>
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/067.bacf5d9e247677b5e3b5624484316580%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
