Cached querysets from Django 4.2 after update to 5.2

Using Django
1

Some of our queries after updating to Django 5.2 are silently producing no results (although our sysadmin claims to have found a postgres(?) error about pickled querysets being Django 4.2). How do I go about clearing those pickled querysets?

[Wed Jun 17 09:34:45.105510 2026] [wsgi:error] [pid 2614813:tid 2614916] [remote 128.112.117.251:50830] /usr/local/tracebase/lib/python3.11/site-packages/django/core/cache/backends/db.py:96: RuntimeWarning: Pickled queryset instance's Django version 4.2.27 does not match the current version 5.2.15.

2

I figured it out. The wording of the warning had thrown me (that and the admin’s paraphrasing of it). My mind had gone to some off the wall magic caching of querysets “behind the scenes” (the admin’s wording). I just cleared the cache table and it started working.