It covers the powerful features of the prompt-toolkit library that is used to make this client.
[append] Off for a specific query, I mean. I think I'd prefer to leave it on by default.
We use `less -XRF` by default. You can change this to whatever you want via the config file `~/.config/litecli/config`. Just uncomment the line that says `# pager = "less -SXRF".
Adding the `-S` to the list of options will make it much better. It will not wrap long lines but instead it will enable horizontal scrolling (using arrow keys).
Check for pager section on this page for some details: https://litecli.com/output/
The other option is to set the `auto_vertical_output = True` in the config file.
This option will cause results to be displayed vertically if they are too wide for the current window.
It does work, but only sort of. Just did:
$ sqlite3 -init select_contact.sql test_sqlite.db
-- Loading resources from select_contact.sql
SQLite version 3.8.11 2015-07-27 13:49:41
Enter ".help" for usage hints.
where select_contact.sql contains "select * from contact;"
So it can run a script given as a parameter.
But it leaves you in the CLI instead of cleanly exiting. And prints those extra headers, etc. Not very Unix-philosophy-adherent, it seems.
I installed it with: $ sudo pip3 install litecli
(seemed to work)
LiteCLI is part of that org. So you can think of it as a clone of mycli that happens to work with SQLite.
The code base is largely similar between mycli and litecli. The changes are to support the SQLite backend and to support the dot commands (like .tables, .mode etc).
So the feature set should be same.
The DBCLI tools are not created by a single individual (anymore). We have a team of core devs and the lead maintainer for pgcli, mycli and litecli are all different people.
'charmap' codec can't encode character u'\xe3' in position 2052: character maps to <undefined>
Feature request: allow for snippet expansion. For instance, when I type 'ssf' + tab, it should expand to Select * From and show the table dropdown.
Without knowing either program very well, how does it compare feature-wise to "DB Browser for SQLite" (apart from the GUI) ?
What would be neccessary if someone would like to integrate it with osqueryi?
We have a large set of tests, but the coverage is no where close to the level that SQLite has.