CHANGELOG 8.1 KB

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