Open fyaconiello opened 5 years ago
Hmm, what does the SQL query say? Which transaction isolation level (and database) are you using?
I'm not doing anything crazy on my Database setup
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
...
'OPTIONS': {
'init_command': "SET sql_mode='STRICT_TRANS_TABLES'",
},
}
}
I'm using RDS's mysql equivelant.
Hmm, what does the SQL query say?
do you just want me to dump the generated sql? What are you looking for here?
My expectation is to use a normal django queryset for the mptt object and get the latest data from the tables, if there is some caching happening at the mptt level, I'd expect it to recache on object save.
The only way I'm able to get my queryset to return correctly what is in the db is to restart the uwsgi process with sudo service uwsgi restart
which isn't something I should have to do to make querysets behave.
I am having the same issue, I see the deleted items which comes from some cache until I restart my docker containers... I am using django==2.1.7 and django-mptt==0.9.1
@koztay and @fyaconiello did you ever get this figured out? I am running into a similar issue.
Same here. I'm using django==2.2 & django-mptt==0.11.0
I am using 0.9.0 of django-mptt and 1.11.x of django core
Issue
After updating an MPTT managed model, I am getting cached old versions of content back from queries.
Note: I have memcache set up on my staging and production environments but have not set up any additional caching mechanism for this feature.
My model:
my admin looks like this:
So if I had the following:
and then updated
AA
to beAA??
I still getAA
back fromCategory.objects.filter(is_active=1)