🎵 Celiz Davidad 🎶

Sorry about the slow response; I've been on vacation! Oh man, those docs are completely wrong. They actually reflect how I wanted the interface to be. I must have never...

Unfortunately no. But that method could (and should) totally be changed to accept a conditions hash that can just be passed through to a `where` call!

Update: this is gonna get fixed, just got a new computer today! Once it's set up and I'm back in the swing of things, this'll be the first thing I...

Ah I forgot that this query is entirely ID-based. Right now I just grab the first 10 (by default) IDs sorted by rank in the ZSET that stores recommendations and...

Hey. I implemented that supposedly database-compatible way to do this in that above commit. Can you please try bundling off of master? I'd like to get this tested across several...

Note that with this change, these methods technically won't _need_ to handle limit or offset anymore, so I'd like to remove that logic entirely. Because of that interface change, I'm...

Hey @alexanderisora, without looking at some code, that's gonna be a tough one to debug. Do you think you'd be able to reproduce this in a new Rails app that...

Legacy databases are an edge case, I think. That being said, perhaps it's time to introduce a per-recommendable configuration, kind of like what you suggested with the latter, and just...

I've been thinking about this as well, but it raises more questions. How many people do we think are actually going to jump on the UUID PK thing? It's not...

At this point, changing likes, dislikes, etc. to using sorting sets would be a breaking change that would require a migration for all users. This may be a better (or...