Does this gem support "setex" call

[madeyemoody85]

I have a use case where I would like to use "SETEX" call to set the key with expiration in single call. Currently I am doing this in two separate calls and if possible I would like to avoid one extra call to redis

[nateware]

I do not believe this is currently supported, but it seems like a great addition. I would be willing to accept a patch with tests to add this functionality. We would probably need to check for the version of Redis, and/or for the existence of SETEX to support older Redis servers.

…

On Fri, Feb 10, 2017 at 7:54 AM Nachiket Londhe ***@***.***> wrote: I have a use case where I would like to use "SETEX" call to set the key with expiration in single call. Currently I am doing this in two separate calls and if possible I would like to avoid one extra call to redis — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#205>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAcoOZf8JUpDxnsSr1Xsp7A-OVgzwzdks5rbIhNgaJpZM4L9iHE> .

[madeyemoody85]

Great I will try my best to get it out this week end, take a look if you would like On Fri, Feb 10, 2017 at 11:48 AM, Nate Wiger <[email protected]> wrote:

…

I do not believe this is currently supported, but it seems like a great addition. I would be willing to accept a patch with tests to add this functionality. We would probably need to check for the version of Redis, and/or for the existence of SETEX to support older Redis servers. On Fri, Feb 10, 2017 at 7:54 AM Nachiket Londhe ***@***.***> wrote: > I have a use case where I would like to use "SETEX" call to set the key > with expiration in single call. Currently I am doing this in two separate > calls and if possible I would like to avoid one extra call to redis > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#205>, or mute the thread > <https://github.com/notifications/unsubscribe- auth/AAAcoOZf8JUpDxnsSr1Xsp7A-OVgzwzdks5rbIhNgaJpZM4L9iHE> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#205 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQSGphEWxnW3ZQUpRsT5ShC8VB4WYt6Cks5rbJTxgaJpZM4L9iHE> .