CHANGELOG 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243
  1. v0.6.6 (2011-xx-xx)
  2. * Switched to Redis 2.2 as the default server profile (there are no changes
  3. that would break compatibility with previous releases).
  4. * Added a VERSION constant to Predis\Client.
  5. * Some performance improvements for multibulk replies (parsing them is about
  6. 16% faster than the previous version).
  7. * Added a new and optional protocol reader, more lightweight and faster than
  8. the default handlers-based one. Users can also specify a custom protocol
  9. reader using the new 'reader' client option.
  10. * Added support for connecting to Redis using UNIX domain sockets (ISSUE #25).
  11. * The "read_write_timeout" connection parameter can now be set to 0 or false
  12. to disable read and write timeouts on connections. The old behaviour of -1
  13. is still intact.
  14. * ZUNIONSTORE and ZINTERSTORE can accept an array to specify a list of the
  15. source keys to be used to populate the destination key.
  16. * MGET, SINTER, SUNION and SDIFF can accept an array to specify the list of
  17. keys. SINTERSTORE, SUNIONSTORE and SDIFFSTORE can also accept an array to
  18. specify the list of source keys.
  19. * SUBSCRIBE and PSUBSCRIBE can accept a list of channels for subscription.
  20. * FIX: some client-side clean-ups for MULTI/EXEC were handled incorrectly in
  21. a couple of corner cases. See also ISSUE #27.
  22. v0.6.5 (2011-02-12)
  23. * FIX: due to an untested internal change introduced in v0.6.4, a wrong
  24. handling of bulk reads of zero-length values was producing protocol
  25. desynchronization errors (ISSUE #20).
  26. v0.6.4 (2011-02-12)
  27. * Various performance improvements (15% ~ 25%) especially when dealing with
  28. long multibulk replies or when using clustered connections.
  29. * Added the "on_retry" option to Predis\MultiExecBlock that can be used to
  30. specify an external callback (or any callable object) that gets invoked
  31. whenever a transaction is aborted by the server.
  32. * Added inline (p)subscribtion via options when initializing an instance of
  33. Predis\PubSubContext.
  34. v0.6.3 (2011-01-01)
  35. * New commands available in the Redis v2.2 profile (dev):
  36. - Strings: SETRANGE, GETRANGE, SETBIT, GETBIT
  37. - Lists : BRPOPLPUSH
  38. * The abstraction for MULTI/EXEC transactions has been dramatically improved
  39. by providing support for check-and-set (CAS) operations when using Redis >=
  40. 2.2. Aborted transactions can also be optionally replayed in automatic up
  41. to a user-defined number of times, after which a Predis\AbortedMultiExec
  42. exception is thrown.
  43. v0.6.2 (2010-11-28)
  44. * Minor internal improvements and clean ups.
  45. * New commands available in the Redis v2.2 profile (dev):
  46. - Strings: STRLEN
  47. - Lists : LINSERT, RPUSHX, LPUSHX
  48. - ZSets : ZREVRANGEBYSCORE
  49. - Misc. : PERSIST
  50. * WATCH also accepts a single array parameter with the keys that should be
  51. monitored during a transaction.
  52. * Improved the behaviour of Predis\MultiExecBlock in certain corner cases.
  53. * Improved parameters checking for the SORT command.
  54. * FIX: the STORE parameter for the SORT command didn't work correctly when
  55. using '0' as the target key (ISSUE #13).
  56. * FIX: the methods for UNWATCH and DISCARD do not break anymore method
  57. chaining with Predis\MultiExecBlock.
  58. v0.6.1 (2010-07-11)
  59. * Minor internal improvements and clean ups.
  60. * New commands available in the Redis v2.2 profile (dev):
  61. - Misc. : WATCH, UNWATCH
  62. * Optional modifiers for ZRANGE, ZREVRANGE and ZRANGEBYSCORE queries are
  63. supported using an associative array passed as the last argument of their
  64. respective methods.
  65. * The LIMIT modifier for ZRANGEBYSCORE can be specified using either:
  66. - an indexed array: array($offset, $count)
  67. - an associative array: array('offset' => $offset, 'count' => $count)
  68. * The method Predis\Client::__construct() now accepts also instances of
  69. Predis\ConnectionParameters.
  70. * Predis\MultiExecBlock and Predis\PubSubContext now throw an exception
  71. when trying to create their instances using a profile that does not
  72. support the required Redis commands or when the client is connected to
  73. a cluster of connections.
  74. * Various improvements to Predis\MultiExecBlock:
  75. - fixes and more consistent behaviour across various usage cases.
  76. - support for WATCH and UNWATCH when using the current development
  77. profile (Redis v2.2) and aborted transactions.
  78. * New signature for Predis\Client::multiExec() which is now able to accept
  79. an array of options for the underlying instance of Predis\MultiExecBlock.
  80. Backwards compatibility with previous releases of Predis is ensured.
  81. * New signature for Predis\Client::pipeline() which is now able to accept
  82. an array of options for the underlying instance of Predis\CommandPipeline.
  83. Backwards compatibility with previous releases of Predis is ensured.
  84. The method Predis\Client::pipelineSafe() is to be considered deprecated.
  85. * FIX: The WEIGHT modifier for ZUNIONSTORE and ZINTERSTORE was handled
  86. incorrectly with more than two weights specified.
  87. v0.6.0 (2010-05-24)
  88. * Switched to the new multi-bulk request protocol for all of the commands
  89. in the Redis 1.2 and Redis 2.0 profiles. Inline and bulk requests are now
  90. deprecated as they will be removed in future releases of Redis.
  91. * The default server profile is "2.0" (targeting Redis 2.0.x). If you are
  92. using older versions of Redis, it is highly recommended that you specify
  93. which server profile the client should use (e.g. "1.2" when connecting
  94. to instances of Redis 1.2.x).
  95. * Support for Redis 1.0 is now optional and it is provided by requiring
  96. 'Predis_Compatibility.php' before creating an instance of Predis\Client.
  97. * New commands added to the Redis 2.0 profile since Predis 0.5.1:
  98. - Strings: SETEX, APPEND, SUBSTR
  99. - ZSets : ZCOUNT, ZRANK, ZUNIONSTORE, ZINTERSTORE, ZREMBYRANK, ZREVRANK
  100. - Hashes : HSET, HSETNX, HMSET, HINCRBY, HGET, HMGET, HDEL, HEXISTS,
  101. HLEN, HKEYS, HVALS, HGETALL
  102. - PubSub : PUBLISH, SUBSCRIBE, UNSUBSCRIBE
  103. - Misc. : DISCARD, CONFIG
  104. * Introduced client-level options with the new Predis\ClientOptions class.
  105. Options can be passed to Predis\Client::__construct in its second argument
  106. as an array or an instance of Predis\ClientOptions. For brevity's sake and
  107. compatibility with older versions, the constructor of Predis\Client still
  108. accepts an instance of Predis\RedisServerProfile in its second argument.
  109. The currently supported client options are:
  110. - profile [default: "2.0" as of Predis 0.6.0]
  111. specifies which server profile to use when connecting to Redis. This
  112. option accepts an instance of Predis\RedisServerProfile or a string
  113. that indicates the target version.
  114. - key_distribution [default: Predis\Distribution\HashRing]
  115. specifies which key distribution strategy to use to distribute keys
  116. among the servers that compose a cluster. This option accepts an
  117. instance of Predis\Distribution\IDistributionStrategy so that users
  118. can implement their own key distribution strategy. Optionally, the new
  119. Predis\Distribution\KetamaPureRing class also provides a pure-PHP
  120. implementation of the same algorithm used by libketama.
  121. - throw_on_error [default: TRUE]
  122. server errors can optionally be handled "silently": instead of throwing
  123. an exception, the client returns an error response type.
  124. - iterable_multibulk [EXPERIMENTAL - default: FALSE]
  125. in addition to the classic way of fetching a whole multibulk reply
  126. into an array, the client can now optionally stream a multibulk reply
  127. down to the user code by using PHP iterators. It is just a little bit
  128. slower, but it can save a lot of memory in certain scenarios.
  129. * New parameters for connections:
  130. - alias [default: not set]
  131. every connection can now be identified by an alias that is useful to
  132. get a certain connection when connected to a cluster of Redis servers.
  133. - weight [default: not set]
  134. allows the client to balance the keys asymmetrically across multiple
  135. servers. This might be useful when you have servers with different
  136. amounts of memory and you want to distribute the load of your keys
  137. accordingly.
  138. - connection_async [default: FALSE]
  139. estabilish connections to servers in a non-blocking way, so that the
  140. client is not blocked while the underlying resource performs the actual
  141. connection.
  142. - connection_persistent [default: FALSE]
  143. the underlying connection resource is left open when a script ends its
  144. lifecycle. Persistent connections can lead to unpredictable or strange
  145. behaviours, so they should be used with extreme care.
  146. * Introduced the Predis\Pipeline\IPipelineExecutor interface. Classes that
  147. implements this interface are used internally by the Predis\CommandPipeline
  148. class to change the behaviour of the pipeline when writing/reading commands
  149. from one or multiple servers. Here is the list of the default executors:
  150. - Predis\Pipeline\StandardExecutor
  151. Exceptions generated by server errors might be thrown depending on the
  152. options passed to the client (see "throw_on_error"). Instead, protocol
  153. or network errors always throw exceptions. This is the default executor
  154. for single and clustered connections and shares the same behaviour of
  155. Predis 0.5.x.
  156. - Predis\Pipeline\SafeExecutor
  157. Exceptions generated by server, protocol or network errors are not
  158. thrown, instead they are returned in the response array as instances of
  159. ResponseError or CommunicationException.
  160. - Predis\Pipeline\SafeClusterExecutor
  161. This executor shares the same behaviour of Predis\Pipeline\SafeExecutor
  162. but it is geared towards clustered connections.
  163. * Support for PUBSUB is handled by the new Predis\PubSubContext class, which
  164. could also be used to build a callback dispatcher for PUBSUB scenarios.
  165. * When connected to a cluster of connections, it is now possible to get a
  166. new Predis\Client instance for a single connection of the cluster by
  167. passing its alias/index to the new Predis\Client::getClientFor() method.
  168. * CommandPipeline and MultiExecBlock return their instances when invoking
  169. commands, thus allowing method chaining in pipelines and multi-exec blocks.
  170. * MultiExecBlock instances can handle the new DISCARD command.
  171. * Connections now support float values for the connection_timeout parameter
  172. to express timeouts with a microsecond resolution.
  173. * FIX: TCP connections now respect the read/write timeout parameter when
  174. reading the payload of server responses. Previously, stream_get_contents()
  175. was being used internally to read data from a connection but it looks like
  176. PHP does not honour the specified timeout for socket streams when inside
  177. this function.
  178. * FIX: The GET parameter for the SORT command now accepts also multiple key
  179. patterns by passing an array of strings. (ISSUE #1).
  180. * FIX: Replies to the DEL command return the number of elements deleted by
  181. the server and not 0 or 1 interpreted as a boolean response. (ISSUE #4).
  182. v0.5.1 (2010-01-23)
  183. * RPOPLPUSH has been changed from bulk command to inline command in Redis
  184. 1.2.1, so ListPopLastPushHead now extends InlineCommand. The old RPOPLPUSH
  185. behavior is still available via the ListPopLastPushHeadBulk class so that
  186. you can override the server profile if you need the old (and uncorrect)
  187. behaviour when connecting to a Redis 1.2.0 instance.
  188. * Added missing support for BGREWRITEAOF for Redis >= 1.2.0
  189. * Implemented a factory method for the RedisServerProfile class to ease the
  190. creation of new server profile instances based on a version string.
  191. v0.5.0 (2010-01-09)
  192. * First versioned release of Predis