New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed RedisClient.zcount. #467

Merged
merged 1 commit into from Jan 17, 2014

Conversation

Projects
None yet
3 participants
@klickverbot
Contributor

klickverbot commented Jan 17, 2014

Note: I did not actually test ZCOUNT because I ended up not
going for Redis in my current project, but this caught my
eye while perusing the implementation.

Fixed RedisClient.zcount.
Note: I did not actually test ZCOUNT because I ended up not
going for Redis in my current project, but this caught my
eye while perusing the implementation.
@Extrawurst

This comment has been minimized.

Show comment
Hide comment
@Extrawurst

Extrawurst Jan 17, 2014

Contributor

what else did u end up using instead ?

Contributor

Extrawurst commented Jan 17, 2014

what else did u end up using instead ?

@klickverbot

This comment has been minimized.

Show comment
Hide comment
@klickverbot

klickverbot Jan 17, 2014

Contributor

I left the caching part for later and just store some temporary results in MongoDB. If it becomes an issue later (unlikely), I'll revisit Redis.

Contributor

klickverbot commented Jan 17, 2014

I left the caching part for later and just store some temporary results in MongoDB. If it becomes an issue later (unlikely), I'll revisit Redis.

s-ludwig added a commit that referenced this pull request Jan 17, 2014

@s-ludwig s-ludwig merged commit 4925b1d into vibe-d:master Jan 17, 2014

@klickverbot klickverbot deleted the klickverbot:redis-zcount branch Jan 17, 2014

@s-ludwig

This comment has been minimized.

Show comment
Hide comment
@s-ludwig

s-ludwig Jan 17, 2014

Member

Thanks for the fix. I'm actually in the same unfortunate situation and don't actually use Redis (yet).

Member

s-ludwig commented Jan 17, 2014

Thanks for the fix. I'm actually in the same unfortunate situation and don't actually use Redis (yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment