12:16:10 GMT <xdexter> Hello, my redis keys are disappear before ttl expiring, someone can help me? I'm doing tests without applications, keys that i created manually on redis disappear too.
14:54:11 GMT <prestorium> Hi all. I have a (I think) conceptual doubt: I did SET foo 'bar'. Then I do 2 simultaneous requests (from 2 different clients): GET foo and SET foo '42'. What happens?
14:54:33 GMT <prestorium> I don't know if this is the right term, but is SET atomic?
14:59:32 GMT <ahfeel> prestorium: SET is atomic, but GET+SET isnt
14:59:42 GMT <ahfeel> you can do a multi() call to make it atomic
14:59:56 GMT <ahfeel> minus: you around ? :)
15:31:14 GMT <prestorium> ahfeel so, if I have 2 clients, one SETing and the other GETing, I _may_ get an undefined behaviour?
15:33:33 GMT <ahfeel> prestorium: well, if the GET happens before any SET, or at the "same time", you may get an "outdated" value
15:33:41 GMT <ahfeel> but that's normal, just like in a normal database
15:34:01 GMT <prestorium> ahfeel "outdated" value is fine. :)
15:35:00 GMT <prestorium> I was worried that "at the same time" could mean an error to the user GETing exactly when redis were writing the new value.
16:10:52 GMT <ahfeel> prestorium: no, no way to get an error :)