http://redis.io/commands/set > *Status code reply: always OK since SET can't... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		nbpoole on March 26, 2012 \| parent \| context \| favorite \| on: Redis persistence demystified http://redis.io/commands/set > Status code reply: always OK since SET can't fail. So, what kind of situation are you envisioning?

giulianob on March 26, 2012 [–]

Maybe SET wasnt a good example .. but lets say you are writing to the wrong type or something like that. I know that its unlikely something will fail in production like that since you should catch it during dev but bugs can happen.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact