1. 14 10月, 2014 1 次提交
  2. 19 1月, 2013 1 次提交
  3. 09 11月, 2012 1 次提交
  4. 31 10月, 2012 1 次提交
  5. 02 6月, 2012 1 次提交
    • A
      Fixed RESTORE hash failure (Issue #532) · 51857c7e
      Alex Mitrofanov 提交于
      (additional commit notes by antirez@gmail.com):
      
      The rdbIsObjectType() macro was not updated when the new RDB object type
      of ziplist encoded hashes was added.
      
      As a result RESTORE, that uses rdbLoadObjectType(), failed when a
      ziplist encoded hash was loaded.
      This does not affected normal RDB loading because in that case we use
      the lower-level function rdbLoadType().
      
      The commit also adds a regression test.
      51857c7e
  6. 24 4月, 2012 1 次提交
  7. 10 4月, 2012 1 次提交
  8. 31 3月, 2012 1 次提交
  9. 03 1月, 2012 1 次提交
  10. 10 11月, 2011 1 次提交
  11. 09 11月, 2011 1 次提交
    • A
      Initial support for key expire times with millisecond resolution. RDB version... · 7dcc10b6
      antirez 提交于
      Initial support for key expire times with millisecond resolution. RDB version is now 3, new opcoded added for high resolution times. Redis is still able to correctly load RDB version 2. Tests passing but still a work in progress. API to specify milliseconds expires still missing, but the precision of normal expires is now already improved and working.
      7dcc10b6
  12. 14 5月, 2011 2 次提交
  13. 13 5月, 2011 1 次提交