-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Inner joins shouldn't work when used to join the same table with itself #270
Comments
Just found this issue, after submitting this request: #652 (comment) Might they be related? |
That's exactly what I'm after. Just to clarify: the feature you're talking about – subqueries – is not yet implemented, right? |
jvshahid
added a commit
that referenced
this issue
Sep 11, 2014
Since we return an error if the same series has more than one alias this fixes #270
This will be fixed as part of #72 |
jvshahid
added a commit
that referenced
this issue
Oct 9, 2014
Since we return an error if the same series has more than one alias this fixes #270
jvshahid
added a commit
that referenced
this issue
Oct 10, 2014
Since we return an error if the same series has more than one alias this fixes #270
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The server should return an error message if the user tried to join the same query with itself. The reason is, where conditions are applied after the two time series are joined, the most common use case of joining a subset of a time series with another subset won't work. Instead, the user should use subqueries to select the two subsets and apply a where condition on the result.
The text was updated successfully, but these errors were encountered: