Skip to content

Issues: jugglingdb/redis-hq-adapter

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.

Sign up for GitHub

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

10 Open 16 Closed
10 Open 16 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Backyard: don't allow adding index values longer than maxlength when timeout > 0
#34 opened Nov 18, 2014 by randunel
Connecting to shutdown server
#33 opened Nov 11, 2014 by 1602
Model properties polluted from old indices
#31 opened May 1, 2014 by randunel
error handling -1 as a reply
#29 opened Apr 9, 2014 by jmgunn87
1
Problems with multiple inq.
#26 opened Jan 22, 2014 by qubyte
2
If MULTI includes several SET commands for the same object, only the last should be applied enhancement
#10 opened Aug 21, 2013 by marcusgreenwood
@1602
JugglingDB doesnt creates incorrect Index when value field is defined as a string false
#7 opened Jun 5, 2013 by agurha
JugglingDB doesnt creates index for boolean value field
#6 opened Jun 5, 2013 by agurha
model.all({ where: { id: [ids] }}, ...) doesn't sort correctly bug
#4 opened May 30, 2013 by marcusgreenwood
@1602
"MGET ZRANGE z:Type:index offset limit" and global ID for all types enhancement
#3 opened Apr 19, 2013 by marcusgreenwood
@1602
2
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.