|
@@ -1,15 +1,8 @@
|
|
|
-v0.8.0 (201x-xx-xx)
|
|
|
+v0.8.0 (2012-1x-xx)
|
|
|
===============================================================================
|
|
|
|
|
|
- The default server profile for Redis is now `2.6`.
|
|
|
|
|
|
-- Added smart support for redis-cluster (Redis v3.0) in addition to the usual
|
|
|
- cluster implementation that uses client-side sharding.
|
|
|
-
|
|
|
-- Some namespaces and classes have been renamed to follow one common rule
|
|
|
- inspired by the Symfony2 naming conventions. See `CHANGELOG.NAMING.md` for
|
|
|
- more details about these changes.
|
|
|
-
|
|
|
- Certain connection parameters have been renamed:
|
|
|
|
|
|
- `connection_async` is now `async_connect`
|
|
@@ -17,37 +10,43 @@ v0.8.0 (201x-xx-xx)
|
|
|
- `connection_persistent` is now `persistent`
|
|
|
|
|
|
- The `throw_errors` connection parameter has been removed and replaced by the
|
|
|
- new `exceptions` client option since exceptions on -ERR replies returned by
|
|
|
- Redis are not generated by connection classes anymore, but are thrown by the
|
|
|
- client class and other abstractions such as pipeline contexts.
|
|
|
+ new `exceptions` client option since exceptions on `-ERR` replies returned by
|
|
|
+ Redis are not generated by connection classes anymore but instead are thrown
|
|
|
+ by the client class and other abstractions such as pipeline contexts.
|
|
|
+
|
|
|
+- Added smart support for redis-cluster (Redis v3.0) in addition to the usual
|
|
|
+ cluster implementation that uses client-side sharding.
|
|
|
+
|
|
|
+- Various namespaces and classes have been renamed to follow rules inspired by
|
|
|
+ the Symfony2 naming conventions.
|
|
|
|
|
|
-- The second argument of `Predis\Client` constructor do not accept strings or
|
|
|
- instances of `Predis\Profile\ServerProfileInterface` anymore. To specify a
|
|
|
- server profile you must explicitly set `profile` in the array of client
|
|
|
- options.
|
|
|
+- The second argument of the constructor of `Predis\Client` does not accept
|
|
|
+ strings or instances of `Predis\Profile\ServerProfileInterface` anymore.
|
|
|
+ To specify a server profile you must explicitly set `profile` in the array
|
|
|
+ of client options.
|
|
|
|
|
|
- `Predis\Command\ScriptedCommand` internally relies on `EVALSHA` instead of
|
|
|
`EVAL` thus avoiding to send Lua scripts bodies on each request. The client
|
|
|
automatically resends the command falling back to `EVAL` when Redis returns a
|
|
|
`-NOSCRIPT` error. Automatic fallback to `EVAL` does not work with pipelines,
|
|
|
- inside a MULTI / EXEC context or with plain `EVALSHA` commands.
|
|
|
+ inside a `MULTI / EXEC` context or with plain `EVALSHA` commands.
|
|
|
+
|
|
|
+- Complex responses are no more parsed by connection classes as they must be
|
|
|
+ processed by consumer classes using the handler associated to the issued
|
|
|
+ command. This means that executing commands directly on connections only
|
|
|
+ returns simple Redis types, but nothing changes when using `Predis\Client`
|
|
|
+ or the provided abstractions for pipelines and transactions.
|
|
|
|
|
|
- Iterators for multi-bulk replies now skip the response parsing method of the
|
|
|
command that generated the response and are passed directly to user code.
|
|
|
- Pipeline and transaction objects still consume automatically the iterators
|
|
|
- that are present in response elements.
|
|
|
-
|
|
|
-- Command response parsers are no more handled by connection classes but should
|
|
|
- be used by consumers such as Predis\Client. Nothing really changes when using
|
|
|
- Predis\Client, but executing a command directly on a connection instance does
|
|
|
- not return the response parsed using the handler associated to the command.
|
|
|
+ Pipeline and transaction objects still consume automatically iterators.
|
|
|
|
|
|
- Cluster and replication connections now extend a new common interface,
|
|
|
`Predis\Connection\AggregatedConnectionInterface`.
|
|
|
|
|
|
-- The `Predis\Connection\MasterSlaveReplication` connection class now uses an
|
|
|
- external strategy class to handle the logic for checking readable / writable
|
|
|
- commands or Lua scripts.
|
|
|
+- `Predis\Connection\MasterSlaveReplication` now uses an external strategy
|
|
|
+ class to handle the logic for checking readable / writable commands and Lua
|
|
|
+ scripts.
|
|
|
|
|
|
- Command pipelines have been optimized for both speed and code cleanness, but
|
|
|
at the cost of bringing a breaking change in the signature of the interface
|