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
distinct on get_all()/between() #3346
Comments
That seems to be a bug, sorry you ran into it. Pinging @mlucy |
This is indeed a bug. A fix is in CR 2321 by @danielmewes . |
How do I retrieve the server version? |
You'll be able to get the server version from a "pseudo table" starting with RethinkDB 1.16 (it will be in As long as the |
This is in next and v1.15.x. (@danielmewes, despite what I told you in person a second ago, the changes in next were almost exactly analagous to the changes in 1.15.x, it just didn't look like it at first because one of the types had changed so the merge conflict looked much messier than it actually was.) |
@nviennot A fix has been released in RethinkDB 1.15.3 |
nice 👍 |
r.between(:index => :some_index).distinct
does not work. RethinkDB complains that theid
index and thesome_index
index are both being used. However,get_all()
works fine. Example:The text was updated successfully, but these errors were encountered: