1. 08 Jun, 2020 1 commit
    • Oran Agra's avatar
      Avoid rejecting WATCH / UNWATCH, like MULTI/EXEC/DISCARD · 2fa077b0
      Oran Agra authored
      Much like MULTI/EXEC/DISCARD, the WATCH and UNWATCH are not actually
      operating on the database or server state, but instead operate on the
      client state. the client may send them all in one long pipeline and check
      all the responses only at the end, so failing them may lead to a
      mismatch between the client state on the server and the one on the
      client end, and execute the wrong commands (ones that were meant to be
      discarded)
      
      the watched keys are not actually stored in the client struct, but they
      are in fact part of the client state. for instance, they're not cleared
      or moved in SWAPDB or FLUSHDB.
      2fa077b0
  2. 06 Jun, 2020 3 commits
  3. 31 May, 2020 3 commits
  4. 29 May, 2020 3 commits
  5. 28 May, 2020 9 commits
  6. 27 May, 2020 9 commits
  7. 26 May, 2020 6 commits
  8. 25 May, 2020 4 commits
  9. 24 May, 2020 2 commits