Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed #29867 -- Added support for storing None value in caches. #13671

Merged
merged 2 commits into from Dec 17, 2020
Merged

Fixed #29867 -- Added support for storing None value in caches. #13671

merged 2 commits into from Dec 17, 2020

Commits on Dec 17, 2020

  1. Refs #30181 -- Corrected note about storing None in the cache.

    @ngnpope @felixxm
    ngnpope authored and felixxm committed Dec 17, 2020
    Configuration menu
    Copy the full SHA
    d23dad5 View commit details
    Browse the repository at this point in the history

  2. Fixed #29867 -- Added support for storing None value in caches. 

    Many of the cache operations make use of the default argument to the
.get() operation to determine whether the key was found in the cache.
The default value of the default argument is None, so this results in
these operations assuming that None is not stored in the cache when it
actually is. Adding a sentinel object solves this issue.

Unfortunately the unmaintained python-memcached library does not support
a default argument to .get(), so the previous behavior is preserved for
the deprecated MemcachedCache backend.
    @ngnpope @felixxm
    ngnpope authored and felixxm committed Dec 17, 2020
    Configuration menu
    Copy the full SHA
    bb64b99 View commit details
    Browse the repository at this point in the history