-
Notifications
You must be signed in to change notification settings - Fork 64
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
BQL does not include IN expression #263
Comments
This feature would be helpful to run things like this:
Note that separately, for the above to be run, the user must be aware of the field names "name0" and "name1", which are (I think) currently undocumented. |
What is missing is
Each of these changes should be maybe three or four lines -- not hard, and a worthwhile tour of the parts of the BQL->SQL compiler. |
On documentation of columns in the fancy BQL queries: yes, that should go in the cheat sheet we discussed, until someone either determines that the current state of affairs is worth committing to or invents a better one. On |
Labeling "help wanted" because the issue now seems to contain enough material for a new contributor to use it as a starter project. |
Question: do we actually compute the values correctly for this, even if the explicit lists were supported? Would we want to revisit resampling for the restricted population, and running some analysis? Or giving the user the option to do that, especially if we're using a small sample of the available data for most of our analysis?
|
This command is not supported
But with sql_execute it is:
In the longer-tmer, is the intention for SQL to co-exist alongside BQL with a separate entry point? Is there a plan for extending BQL to implement a superset of SQL syntax?
In the short-term, are we intending for users to use sql_execute() as well as execute()? Is there a list of SQL features that are not currently supported by BQL somewhere?
The text was updated successfully, but these errors were encountered: