Opened 5 years ago
Last modified 3 years ago
#31891 new Bug
Inconsistent related field cache invalidation — at Version 1
Description (last modified by ) ¶
Repro:
from django.db import models class AppUser(models.Model): pass class Profile(models.Model): user = models.OneToOneField( to=AppUser, on_delete=models.PROTECT, ) a = AppUser.objects.create() b = AppUser.objects.create() Profile.objects.create(user=a) b.profile # Errors, since it has not been created yet a.profile.user_id = b.id a.profile.save() # Works! Profile.objects.get(user=b) # <Profile: Profile object (1)> b.profile # Errors, since it uses the cached value
I can fix it by using a.profile.user = b
which does the cache invalidation as expected. Or using b.refresh_from_db()
This is a contrived example but the real use-case was cloning a model instance. And instead of erroring it just kept returning the cached value
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Note:
See TracTickets
for help on using tickets.