Tickets :: Comment on [#12088] Need to clear or check cache if compression changes

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .__ . ,. . \|\/\|[ __[__) \./ \|\ \| \| \|[_./[__) \| \| \\|
Comment	>> Once horde_lz4 is stable, or even earlier when user have >> preferred_state=beta set, upgrading with -a will install the >> extension (even though not activating it by default). This will break >> existing caches though > > No it won't. In fact, I have not once cleared my cache that was > previously stored with lzf compression and everything works fine. > > I specifically made sure that horde_lzf fails gracefully if it tries > to decompress non-lz4 compressed data. In this case, it returns > false which counts as a cache-miss. Which is no big deal and > something we do all the time (e.g. changing the serialize format of > an object). > > Sure - if someone upgrades when active sessions are active that > session will likely be terminated. But so what? That could be said > about any number of changes that would break active sessions. We've > never supported in-place upgrading of active sessions.
Attachment
Watch this ticket