-
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
Allow the implicit time field to be renamed #6374
Conversation
@jsternberg Can you set |
The reason why I didn't do that is so there was less code to change and so I didn't have to add that logic to the parser. The diff would be a lot larger if that field is set to I think I'm going to rename |
49a80fb
to
ed9f8c8
Compare
Can you give some examples of what needs to change? It seems like adding time alias checking everywhere in the future would be error prone. |
It depends on where we set the I also think that checking for the empty string in one place isn't too hard and it only has to be done in one place. |
If it's just test code that's not that bad. We may only have one place to do the |
I don't think that really applies for this. This code does not rename the time field. It is merely a placeholder to hold onto the alias if there is a time present in the query when the query is rewritten. Another location that has to be changed is the code that sets this to begin with. Currently it's just this:
This has to be changed to:
We don't allow aliases to be used in conditions at the moment. Is that something we're supposed to be doing? I don't really see this as affecting subqueries because these values are only used for setting the column names.
If it makes it better, I can add a function to the
|
a3a236e
to
0a03164
Compare
OK, leave off the |
Otherwise lgtm |
0a03164
to
9d01f3a
Compare
LGTM 👍 |
Fixes #6296.