GitHub - dinedal/textql: Execute SQL against structured text like CSV or TSV
source link: https://github.com/dinedal/textql
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Readme.md
TextQL
Allows you to easily execute SQL against structured text like CSV or TSV.
Example session:
Major changes!
Since there has been some time since the initial release of textql, I've made some improvements as well as made the project much more modular. There's also been a additional performance tweaks and added functionality, but this comes at the cost of breaking the original command line flags and changing the install command.
Changes since v1
Additions:
- Numeric values are automatically recognized in more cases.
- Date / Time / DateTime values are automatically recognized in reasonable formats. See Time Strings for a list for accepted formats, and how to convert from other formats.
- Added join support! Multiple files / directories can be loaded by listing them at the end of the command.
- Directories are read by reading each file inside, and this is non-recursive.
- You can list as many files / directories as you like.
- Added flag '-output-file' to save output directly to a file.
- Added flag '-output-dlm' to modify the output delimiter.
- Added "short SQL" syntax.
- For the case of a single table, the
FROM [table]
can be dropped from the query. - For simple selects, the
SELECT
keyword can be dropped from the query. - This means the v1 command
textql -sql "select * from tbl" -source some_file.csv
can be shortened totextql -sql "*" some_file.csv
- For the case of a single table, the
Changes:
- The flag '-outputHeader' was renamed to '-output-header'.
Removals:
- Dropped the ability to override table names. This makes less sense after the automatic tablename generation based on filename, joins, and shorter SQL syntax changes.
- Removed '-source', any files / paths at the end of the command are used, as well as piped in data.
Bug fixes:
- Writing to a directory no longer fails silently.
Key differences between textql and sqlite importing
- sqlite import will not accept stdin, breaking unix pipes. textql will happily do so.
- textql supports quote escaped delimiters, sqlite does not.
- textql leverages the sqlite in memory database feature as much as possible and only touches disk if asked.
Is it any good?
Requirements
- Go 1.4 or later
Install
Latest release on Homebrew (OS X)
brew install textql
Build from source
go get -u github.com/dinedal/textql/...
Usage
textql [-console] [-save-to path path] [-output-file path] [-output-dlm delimter] [-output-header] [-pretty] [-quiet] [-header] [-dlm delimter] [-sql sql_statements] [path ...] -console After all statements are run, open SQLite3 REPL with this data -dlm string Input delimiter character between fields -dlm=tab for tab, -dlm=0x## to specify a character code in hex (default ",") -header Treat input files as having the first row as a header row -output-dlm string Output delimiter character between fields -output-dlm=tab for tab, -dlm=0x## to specify a character code in hex (default ",") -output-file file Filename to write output to, if empty no output is written (default "stdout") -output-header Display column names in output -quiet Surpress logging -pretty Pretty print output -save-to file SQLite3 db is left on disk at this file -sql string SQL Statement(s) to run on the data -version Print version and exit
License
New MIT License - Copyright (c) 2015, 2016 Paul Bergeron http://pauldbergeron.com/
See LICENSE for details
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK