would be nice to provide a query directly when running the program

[sanga]

i.e.

influx-cli -db=timeseries -q=[query]

or perhaps the query could just be a positional argument (that's how postgres does that as I recall). My particular reason for this is to pipe to less but there's many other reasons too.

[Dieterbe]

yep. i also want this and i can easily implement this.

note, you can already write one or more queries to stdin and that'll work too
example

echo -e "list series\nselect foo from bar" | influx-cli

OR

influx-cli  <<< "list series"  # bash built-in to write to stdin

[Dieterbe]

done!

[sanga]

cheers!

[sanga]

oh and thank you for publishing this excellent tool. Much more convenient than curl ;)

[sanga]

Still one complaint about this actually. When executing with a query it would seem more natural to me, to have influx-cli to exit once the query is complete, not drop into the shell.

[Dieterbe]

But then you could just as well do influx-cli <<< "your queries"? providing queries as args or on stdin would be equivalent (because the latter already runs influx-cli in non-interactive mode and exits the program when it's done).
I do agree that your suggestion is probably what most people will expect. (probably... not really sure, would have to try it with mysql/pgsql/vsql/...).
If we do it your way, then there's no easy way to do "i want to run an interactive session, but also execute a few queries first".
but to address the latter I actually want to implement reading from an inputfile, so you could type < filename or something in an interactive session and it would all queries in the file. I'm thinking once we support that, I can change the behavior as you suggested.
thoughts?

[sanga]

Exiting after running a query as a cmdline param is just what I expected coming from psql. From my perspective it's OK as it is now (I hadn't realised that <<< would achieve what I wanted). If more people complain about this, then I guess you should review whether to better document or change that behaviour

[Dieterbe]

fwiw that issue is now being discussed in #5