CHANGELOG 12 KB

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