4 ms·
It's written in Python, and seems to use SQLite under the hood. I guess it just applies tokenization and throws the text into a temporary database. Quite simi
by unwind 13y ago
It's written in Python, and seems to use SQLite under the hood.
I guess it just applies tokenization and throws the text into a temporary database.
Quite similar to the Go project https://github.com/dinedal/textql https://github.com/dinedal/textql, at least superficially.
- j_s 13y agoA lot of similar tools were discussed when that Go project came up 3 weeks ago: https://news.ycombinator.com/item?id=7175830 https://news.ycombinator.com/item?id=7175830 > MS ADO / ODBC > Perl DBI > npm j (with jqa) > Ruby (csv2sqlite) > Python (csvkit) > Go (textql, comp) > Java (optiq, openrefine, H2 SQL) > R (sqldf) > Haskell (txt-sushi) > XML (xmlstarlet, xmllint, xmlstar) > HTML (HtmlAgilityPack, Chrome $x()) > Postgres file_fdw > Oracle external tables > SQL Server OPENDATASOURCE and OPENQUERY > Log file viewers (MS LogParser, Apache asql, lnav)
- harelba 13y agoHi, I'm q's creator, Harel. There are obviously lots of other software which can provide a similar capability, and while I haven't checked all of them out, I'm really believe that most of them do a great job. However, my rationale for creating this tool was to provide a seamless addition to the Linux command line toolset - A tool as most Linux commands are, and not a capability. The distinction I'm doing here is that tools are reusable, composable and such, vs a capability which is usually less reusable in different contexts. I'm sure that some of the above are definitely tools. I just hope that the tool I have created provides value to people and helps them with their tasks. As I posted here elsewhere, my complete rationale for creating the tool is available on the README of the github project. Comments and issues are most welcome. Harel Ben-Attia