-
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
Feature request: InfluxQL comments #8025
Comments
I've found myself reaching for the |
We technically already have multiline commands. Whitespace is mostly ignored so you can split a command between multiple lines pretty easily (although the CLI does not support it, but that's different than the server not supporting it). I think this should be fairly easy to do and is a nice little feature. Thoughts @pauldix? |
Also, what's the settled syntax for this? |
Agreed, no need to support nested multiline comments. Supporting `--` for
single line and `/* */` for multiline seems sufficient to me.
…On Mon, Feb 27, 2017 at 8:45 AM, Jonathan A. Sternberg < ***@***.***> wrote:
Also, what's the settled syntax for this? -- for single line comments and /*
*/ for multiline comments? Should we support nested multiline comments
such as /* /* */ */? I vote no on the latter, but I thought I would bring
it up anyway as some programming languages like D support that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8025 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARvV50cbNr3q6KAFCm-_WmptGt7mqsMks5rgv2MgaJpZM4MEr4f>
.
|
LGTM. Although I am wondering if people will also try |
Proposal: Comments in InfluxQL.
Current behavior: Comments are not supported.
Desired behavior: Allow line-oriented comments in InfluxQL. Example:
Use case: When performing data analysis, I end up using scripting pipelines that look like this:
Inside
my_query.influxql
I have no way to document the queries (and now, subqueries). Comments would increase maintainability.The text was updated successfully, but these errors were encountered: