You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2022. It is now read-only.
Jussi,
the short answer is No.
At the moment, transactions don't use WATCH and therefore there is no guarantee that keys taking part in the transaction have changed by the time we issue the EXEC command.
The good news is, once redis 2.6 is out, there will not be a need for WATCH in stdnet.
The transaction will be issued as a lua script, atomically, with WATCH part of the script.
This will be in stdnet 0.7
I noticed that there is a redis client implementation in the stdnet. Any thoughts on using redis-py and stdnet concurrently in the same python session?
I was thinking that I could implement my data structures with stdnet, but create the CAS procedure keys directly to Redis. It looks like Redis 2.6 is not quite here yet and I'd like to get my testing underway. Thus I might use redis-py and stdnet at the same time, but with separate connections to Redis.
That should be fine. You can use stdnet to manage and retrieve your data, and use redis-py for your specific needs. You could also use the internal (redis-py) client by doing something like this:
Hi.
Stdnet looks like a very powerful, yet simple ORM. I read the docs and tried looking through the code for transaction support.
I have an use case almost exactly like in the Redis docs:
http://redis.io/topics/transactions -> section on optimistic locking and check-and-set
Does transactions with Stdnet support WATCH command?
My thanks.
Jussi
The text was updated successfully, but these errors were encountered: