CHANGELOG 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197
  1. v0.7.0 (2010-xx-xx)
  2. * Support for long aliases (method names) for Redis commands has been dropped.
  3. * List of the methods removed in this release:
  4. - Predis\Client::create()
  5. This method has been removed because it was considered redundant
  6. with Predis\Client::__construct() since Predis 0.6.0.
  7. - Predis\Client::pipelineSafe()
  8. This method was deprecated in Predis 0.6.1 and now it has been finally
  9. removed. Use Predis\Client::pipeline(array('safe' => true)).
  10. * The Predis\MultiBulkCommand class has been merged into Predis\Command and
  11. thus removed. If you have code that extends Predis\MultiBulkCommand but
  12. you can not afford to update your code, you can always implement it again
  13. as an abstract class simply by extending Predis\Command.
  14. * The Predis\IConnection interface has been splitted in two different new
  15. interfaces: Predis\IConnectionSingle and Predis\IConnectionCluster.
  16. * Developers can now register their own classes that implements the
  17. Predis\IConnectionSingle interface to handle different URI schemes such as
  18. 'redis', 'tcp', 'udp' or anything else. Everything is handled by the
  19. new Predis\ConnectionFactory class.
  20. * Added the new Predis\ICommand interface. The Predis\Command class now
  21. implements this interface that is used in the core bits of Predis.
  22. * Implicit extraction of arguments when the only argument passed to a
  23. multibulk command is an array is not supported anymore and must be done
  24. explicitly inside Predis\Command::filterArguments().
  25. * It is now possible to pass instances of Predis\ConnectionParameters and
  26. Predis\IConnection as parameters of Predis\Client::__construct().
  27. v0.6.1 (2010-07-11)
  28. * Minor internal improvements and clean ups.
  29. * New commands available in the Redis v2.2 profile (dev):
  30. - Misc. : WATCH, UNWATCH
  31. * Optional modifiers for ZRANGE, ZREVRANGE and ZRANGEBYSCORE queries are
  32. supported using an associative array passed as the last argument of their
  33. respective methods.
  34. * The LIMIT modifier for ZRANGEBYSCORE can be specified using either:
  35. - an indexed array: array($offset, $count)
  36. - an associative array: array('offset' => $offset, 'count' => $count)
  37. * The method Predis\Client::__construct() now accepts also instances of
  38. Predis\ConnectionParameters.
  39. * Predis\MultiExecBlock and Predis\PubSubContext now throw an exception
  40. when trying to create their instances using a profile that does not
  41. support the required Redis commands or when the client is connected to
  42. a cluster of connections.
  43. * Various improvements to Predis\MultiExecBlock:
  44. - fixes and more consistent behaviour across various usage cases.
  45. - support for WATCH and UNWATCH when using the current development
  46. profile (Redis v2.2) and aborted transactions.
  47. * New signature for Predis\Client::multiExec() which is now able to accept
  48. an array of options for the underlying instance of Predis\MultiExecBlock.
  49. Backwards compatibility with previous releases of Predis is ensured.
  50. * New signature for Predis\Client::pipeline() which is now able to accept
  51. an array of options for the underlying instance of Predis\CommandPipeline.
  52. Backwards compatibility with previous releases of Predis is ensured.
  53. The method Predis\Client::pipelineSafe() is to be considered deprecated.
  54. * FIX: The WEIGHT modifier for ZUNIONSTORE and ZINTERSTORE was handled
  55. incorrectly with more than two weights specified.
  56. v0.6.0 (2010-05-24)
  57. * Switched to the new multi-bulk request protocol for all of the commands
  58. in the Redis 1.2 and Redis 2.0 profiles. Inline and bulk requests are now
  59. deprecated as they will be removed in future releases of Redis.
  60. * The default server profile is "2.0" (targeting Redis 2.0.x). If you are
  61. using older versions of Redis, it is highly recommended that you specify
  62. which server profile the client should use (e.g. "1.2" when connecting
  63. to instances of Redis 1.2.x).
  64. * Support for Redis 1.0 is now optional and it is provided by requiring
  65. 'Predis_Compatibility.php' before creating an instance of Predis\Client.
  66. * New commands added to the Redis 2.0 profile since Predis 0.5.1:
  67. - Strings: SETEX, APPEND, SUBSTR
  68. - ZSets : ZCOUNT, ZRANK, ZUNIONSTORE, ZINTERSTORE, ZREMBYRANK, ZREVRANK
  69. - Hashes : HSET, HSETNX, HMSET, HINCRBY, HGET, HMGET, HDEL, HEXISTS,
  70. HLEN, HKEYS, HVALS, HGETALL
  71. - PubSub : PUBLISH, SUBSCRIBE, UNSUBSCRIBE
  72. - Misc. : DISCARD, CONFIG
  73. * Introduced client-level options with the new Predis\ClientOptions class.
  74. Options can be passed to Predis\Client::__construct in its second argument
  75. as an array or an instance of Predis\ClientOptions. For brevity's sake and
  76. compatibility with older versions, the constructor of Predis\Client still
  77. accepts an instance of Predis\RedisServerProfile in its second argument.
  78. The currently supported client options are:
  79. - profile [default: "2.0" as of Predis 0.6.0]
  80. specifies which server profile to use when connecting to Redis. This
  81. option accepts an instance of Predis\RedisServerProfile or a string
  82. that indicates the target version.
  83. - key_distribution [default: Predis\Distribution\HashRing]
  84. specifies which key distribution strategy to use to distribute keys
  85. among the servers that compose a cluster. This option accepts an
  86. instance of Predis\Distribution\IDistributionStrategy so that users
  87. can implement their own key distribution strategy. Optionally, the new
  88. Predis\Distribution\KetamaPureRing class also provides a pure-PHP
  89. implementation of the same algorithm used by libketama.
  90. - throw_on_error [default: TRUE]
  91. server errors can optionally be handled "silently": instead of throwing
  92. an exception, the client returns an error response type.
  93. - iterable_multibulk [EXPERIMENTAL - default: FALSE]
  94. in addition to the classic way of fetching a whole multibulk reply
  95. into an array, the client can now optionally stream a multibulk reply
  96. down to the user code by using PHP iterators. It is just a little bit
  97. slower, but it can save a lot of memory in certain scenarios.
  98. * New parameters for connections:
  99. - alias [default: not set]
  100. every connection can now be identified by an alias that is useful to
  101. get a certain connection when connected to a cluster of Redis servers.
  102. - weight [default: not set]
  103. allows the client to balance the keys asymmetrically across multiple
  104. servers. This might be useful when you have servers with different
  105. amounts of memory and you want to distribute the load of your keys
  106. accordingly.
  107. - connection_async [default: FALSE]
  108. estabilish connections to servers in a non-blocking way, so that the
  109. client is not blocked while the underlying resource performs the actual
  110. connection.
  111. - connection_persistent [default: FALSE]
  112. the underlying connection resource is left open when a script ends its
  113. lifecycle. Persistent connections can lead to unpredictable or strange
  114. behaviours, so they should be used with extreme care.
  115. * Introduced the Predis\Pipeline\IPipelineExecutor interface. Classes that
  116. implements this interface are used internally by the Predis\CommandPipeline
  117. class to change the behaviour of the pipeline when writing/reading commands
  118. from one or multiple servers. Here is the list of the default executors:
  119. - Predis\Pipeline\StandardExecutor
  120. Exceptions generated by server errors might be thrown depending on the
  121. options passed to the client (see "throw_on_error"). Instead, protocol
  122. or network errors always throw exceptions. This is the default executor
  123. for single and clustered connections and shares the same behaviour of
  124. Predis 0.5.x.
  125. - Predis\Pipeline\SafeExecutor
  126. Exceptions generated by server, protocol or network errors are not
  127. thrown, instead they are returned in the response array as instances of
  128. ResponseError or CommunicationException.
  129. - Predis\Pipeline\SafeClusterExecutor
  130. This executor shares the same behaviour of Predis\Pipeline\SafeExecutor
  131. but it is geared towards clustered connections.
  132. * Support for PUBSUB is handled by the new Predis\PubSubContext class, which
  133. could also be used to build a callback dispatcher for PUBSUB scenarios.
  134. * When connected to a cluster of connections, it is now possible to get a
  135. new Predis\Client instance for a single connection of the cluster by
  136. passing its alias/index to the new Predis\Client::getClientFor() method.
  137. * CommandPipeline and MultiExecBlock return their instances when invoking
  138. commands, thus allowing method chaining in pipelines and multi-exec blocks.
  139. * MultiExecBlock instances can handle the new DISCARD command.
  140. * Connections now support float values for the connection_timeout parameter
  141. to express timeouts with a microsecond resolution.
  142. * FIX: TCP connections now respect the read/write timeout parameter when
  143. reading the payload of server responses. Previously, stream_get_contents()
  144. was being used internally to read data from a connection but it looks like
  145. PHP does not honour the specified timeout for socket streams when inside
  146. this function.
  147. * FIX: The GET parameter for the SORT command now accepts also multiple key
  148. patterns by passing an array of strings. (ISSUE #1).
  149. * FIX: Replies to the DEL command return the number of elements deleted by
  150. the server and not 0 or 1 interpreted as a boolean response. (ISSUE #4).
  151. v0.5.1 (2010-01-23)
  152. * RPOPLPUSH has been changed from bulk command to inline command in Redis
  153. 1.2.1, so ListPopLastPushHead now extends InlineCommand. The old RPOPLPUSH
  154. behavior is still available via the ListPopLastPushHeadBulk class so that
  155. you can override the server profile if you need the old (and uncorrect)
  156. behaviour when connecting to a Redis 1.2.0 instance.
  157. * Added missing support for BGREWRITEAOF for Redis >= 1.2.0
  158. * Implemented a factory method for the RedisServerProfile class to ease the
  159. creation of new server profile instances based on a version string.
  160. v0.5.0 (2010-01-09)
  161. * First versioned release of Predis