5 ms·

I really hope I get to use Rethink in anger before I die. Last time, I had to move on because we are multi-tenant SaaS and it seemed the compound indexes just

by troyk 12y ago

I really hope I get to use Rethink in anger before I die. Last time, I had to move on because we are multi-tenant SaaS and it seemed the compound indexes just were not up to that task, does this release fix any of those issues? (I seem to recall I was having to use a between query and not being able to sort, but it was a while ago and I quickly got back to work with old reliable (postgresql))

coffeemug 12y ago
I think you're talking about https://github.com/rethinkdb/rethinkdb/issues/1227 https://github.com/rethinkdb/rethinkdb/issues/1227. It hasn't been fixed yet, and is a big deal for many multitenancy users. I'll bump it up in the roadmap -- sorry it's taking so long to get this fixed. It turns out that everyone only needs 5% of RethinkDB features, but it's always a different 5%. That makes product roadmaps really hard. I think in this sense databases are a bit like word processors :)
- troyk 12y ago
  That seems correct, I saw the issue bump on github, you guys seem like the nicest and brightest engineers around and really hope you guys keep that vibe.
- simonb 12y ago
  another vote for compound indices.
  - coffeemug 12y ago
    Just FYI, you compound indexes are already fully supported -- see http://rethinkdb.com/docs/secondary-indexes/python/ http://rethinkdb.com/docs/secondary-indexes/python/. The particular issue in question is using an index to filter documents, and then ordering them by another index.