Kdyby/Redis requires PHP 7.4 or newer.
$ composer require kdyby/redisLearn more in the documentation.
Homepage http://www.kdyby.org and repository http://github.com/kdyby/Redis.
Full Changelog: v6.1.3...v6.1.4
Full Changelog: v6.1.2...v6.1.3
Full Changelog: v6.1.1...v6.1.2
Full Changelog: v6.1.0...v6.1.1
Full Changelog: v6.0.0...v6.1.0
Thanks @PavelJurasek & @pechondra
Added support for PHP 7.4 and only Nette/Utils 3.0
Removed Nette/Reflection, this package is discontinued.
Class references in test use only standard PHP reflection classes.
PR #85
Coding standard
strict_typesTravis
Composer
\Kdyby\Redis\IRedisDriver::class and \Kdyby\Redis\IRedisDriverOld::class because they had outdated methods and docblocks, needed to be updated with redis changes. Also they had same methods as \Redis and as interfaces they needed to have same type hints as implemented classes wich depends on installed version on client server. All this meant 30+ CS and PHPStan skipped rules and no added value. So use default \Redis hinting and if needed add some undocumented stuff add it in docblok of \Kdyby\Redis\Driver\PhpRedisDriver::class since it is named driver it is appropriate place.class RedisLuaJournal extends RedisJournal implements Nette\Caching\Storages\IJournal -> class RedisLuaJournal extends \Kdyby\Redis\RedisJournalExceptions moved to separate files and changed namespace. For compatibility there is Typo3/ClassAliasLoader with aliased old namespaces. For future uses please use new namespaces.
\Kdyby\Redis\ConnectionException => \Kdyby\Redis\Exception\ConnectionException
\Kdyby\Redis\Exception => \Kdyby\Redis\Exception\IException
\Kdyby\Redis\InvalidArgumentException => \Kdyby\Redis\Exception\InvalidArgumentException
\Kdyby\Redis\LockException => \Kdyby\Redis\Exception\LockException
\Kdyby\Redis\MissingExtensionException => \Kdyby\Redis\Exception\MissingExtensionException
\Kdyby\Redis\RedisClientException => \Kdyby\Redis\Exception\RedisClientException
\Kdyby\Redis\SessionHandlerException => \Kdyby\Redis\Exception\SessionHandlerException
\Kdyby\Redis\TransactionException => \Kdyby\Redis\Exception\TransactionException
\Kdyby\Redis\DI\RedisExtension::PANEL_COUNT_MODE is privateredis.client) is expected string|null\Kdyby\Redis\Diagnostics::TIMER_NAME is private\Kdyby\Redis\Diagnostics\Panel::begin\Kdyby\Redis\Driver\PhpRedisDriverOld::script now accepts only declared arguments, dropped func_get_args\Kdyby\Redis\ExclusiveLock::acquireLock\Kdyby\Redis\ExclusiveLock::release\Kdyby\Redis\ExclusiveLock::increaseLockTimeout\Kdyby\Redis\ExclusiveLock::getLockTimeout\Kdyby\Redis\ExclusiveLock::formatLock\Kdyby\Redis\RedisClient::__construct\Kdyby\Redis\RedisClient::unlock\Kdyby\Redis\RedisClient::lock\Kdyby\Redis\RedisClient::__call\Kdyby\Redis\RedisClient::__get\Kdyby\Redis\RedisClient::__set\Kdyby\Redis\RedisClient::__isset\Kdyby\Redis\RedisJournal and Lua version constants made private\Kdyby\Redis\RedisJournal::write\Kdyby\Redis\RedisJournal::formatKey\Kdyby\Redis\RedisStorage constants made private\Kdyby\Redis\RedisStorage::read\Kdyby\Redis\RedisStorage::lock\Kdyby\Redis\RedisStorage::unlock\Kdyby\Redis\RedisStorage::write\Kdyby\Redis\RedisStorage::removeAnd more, see #85 for all changes
Compatibility with phpredis v3 and v4.
2.1.*2.6~2.1@dev2.0.*RedisStorage::read() when the key was dropped because there wasn't enought memory.Do not install this realease, tests didn't pass on Travis.
redis:
storage: {locks: off}This means the storage is on, and is not using locks.
WARNING: please flush your cache completely before upgrading. The data format is not compatible.
Non-native session handler with locks is back!
I was sad that the native handler doesn't care about locks (which I didn't notice till recently), so I had to revert the old session handler written in PHP. The native is still default, but this pull adds new option to turn it back on
redis:
session:
native: offThere should be no problem in session data compatibility. It should just work.
Also, thanks to @matej21, the journal has new internal structure, which should be exponentially faster on absurd numbers (hundreds of thousands or even milions) of tagged keys.
This new journal takes advantage of Redis's scripting feature. You can create scripts in lua and Redis will execute them for you. This lowers latency and dramatically decreases number of requests that has to be send.
