3 ms·

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, an

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.