Package: termsql
TERMSQLConvert text from a file or from stdin into SQL table and query it instantly. Uses sqlite as backend.
The idea is to make SQL into a tool on the command line or in scripts.InstallRequirements:pythonsqlite3sqlparse module 0.1.15 and up fromhttps://github.com/andialbrecht/sqlparse(optional)To install termsql open a terminal and run:sudo python setup.py installTermsql now supports shorter and more convenient sql statements given the sqlparse module fromhttps://pypi.python.org/pypi/sqlparse/version 0.1.15 or higher is installed.termsql "select col0,col1 from tbl"
#is equal to:
termsql select col0,col1

termsql -m line -1 "select USER,COUNT(*) from tbl group by USER"
#is equal to:
termsql -m line -1 "select USER,COUNT(*) group by USER"Therefore installing the sqlparse module (which is tiny anyway) fromhttps://pypi.python.org/pypi/sqlparse/orhttps://github.com/andialbrecht/sqlparseis highly recommended. At least if you want to save yourself some typing.Learn morealways helpful is:termsql --helpand also:man termsqlOnline manual:http://tobimensch.github.io/termsqlSo what can it do?convert text/CSV files into sqlite database/tablework on stdin data on-the-flyit can be used as swiss army knife kind of tool for extracting information
from other processes that send their information to termsql via a pipe
on the command line or in scriptstermsql can also pipe into another termsql of courseyou can quickly sort and extract datacreates string/integer/float column types automaticallygives you the syntax and power of SQL on the command lineExamplesexport LC_ALL=en_US; top -b | head | termsql -1 -H 6 "select [PID],[USER],[COMMAND],[%CPU] from tbl where [%CPU]>=25"termsql doesn’t recognize numbers like “25,3” as numbers, but as strings. export LC_ALL=en_US ensures that top outputs numbers that are easy for termsql/sqlite to digest (ie. “25.3”). -H 6 makes termsql disregard the first 6 lines. We select only the processes with more than 25% cpu usage and output their PID,USER,COMMAND and %CPU.export DISPLAY=$(ps aux | termsql "select COL11 from tbl where COL10 like '%Xorg.bin%' limit 1")set DISPLAY environment variable to what display X is running on right now, assuming that the X binary is called “Xorg.bin”)ls -lha /usr/bin/* | termsql -w -r 8 "select * from tbl order by COL8 desc"-r 8 merges the filenames into the 8th column. Then “order by COL8 desc” sorts them in reverse order. Due to -w the output looks nice on the command lineps aux | termsql -m line -1 "select USER,COUNT(*) from tbl group by USER"counts the total number of processes that each user has running. -1 gets the column names from the first line, therefore we can use USER instead of COL0 in the SQL statement. “group by USER” groups the rows of with identical USER together and for that reason COUNT(*) returns the total number of rows (in this case processes) for each USER. -m line beautifies the output.termsql -ei .config/Bitcoin/Bitcoin-Qt.conf -c key,value -d = -p = -x "update tbl set value='true' where key='fMinimizeToTray'"Demonstrates how you can use termsql to edit simple config files with key/value pairs. -i loads the config file as input and -e makes sure this same file is written to instead of stdout. Simply speaking: enabling edit mode. -d = sets the delimiter for splitting the input to = and -p = sets the separator for the output to = again, so that the output format matches the input format. -x appends a “;select * from tbl” to the user defined query, so that we get everything back that we put in. The user query is an SQL update statement which sets the value part of the key value pair to true, where the key is fMinimizeToTray. -c key,value allows us to use these convenient names instead of COL0 (key) and COL1 (value). Note that this approach may not always be perfect, for example in .config/Bitcoin/Bitcoin-Qt.conf there’s a section line “[General]” which gets changed to “[General]=” after termsql is done with editing. Which may or may not be a problem depending on the program that uses the config file. It could easily be fixed with a tool like sed though.For detailed information about options and more examples see theManualVs awkawk can’t create permanent sqlite databasessqlite is efficient, fast and mature (not saying that awk isn’t)many people have worked with SQL before that aren’t experts on awkSQL tends to look very descriptive, which should make it easy to maintain code and fix bugstermsql is designed from the start to be as intuitive as possible,
awk doesn’t really strike the author of termsql as intuitive (that’s a personal opinion and
not a fact).termsql can output to CSV,HTML,insert,SQL dump,tcl,text,line,SQlite databaseContributeYou like termsql and want to help in some way? Then why don’t you tell others about it and show them how
they can use it. Post your termsql usecases and ideas on twitter, facebook, google+, your-favorite-social-media,
your blog or website. Making termsql more popular is a great contribution.Another possible way to contribute is to help with improvement or translation of the documentation.It would also be great, if people create packages for their own distribution or file bugreports
for their distribution, so that termsql will be available in their favorite (Linux-)distribution.Of course contributing code/patches is also welcome, look at the roadmap below or at the issues tracker on github
for ideas on what to do or come up with your own ideas. Forking termsql is a great way to start as well.Want to contribute by reporting a problem/bug? Feel free to usethe issue tracker.