CHANGELOG 8.3 KB

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