textql
go-duckdb
| textql | go-duckdb | |
|---|---|---|
| 15 | 4 | |
| 9,030 | 496 | |
| - | - | |
| 3.7 | 8.1 | |
| 6 months ago | about 19 hours ago | |
| Go | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
textql
-
Jaq – A jq clone focused on correctness, speed, and simplicity
I like textql [0] better for this use case, as it's simpler in my mind.
[0] https://github.com/dinedal/textql
-
Can SQL be used without an RDBMS?
Primarily, you are right. SQL is for working with structured data and that largely covers RDBs. However, there are tools (like textql) that allow you to query CSV files and the effort works with most other text files that have some kind of structure.
- Textql: Execute SQL against structured text like CSV or TSV
-
Show HN: ClickHouse-local – a small tool for serverless data analytics
As the author of textql ( https://github.com/dinedal/textql ) - thanks for the shoutout!
Looks great, I love more options in the space for CLI based data analysis tools! Fantastic work!
- Using Commandline To Process CSV files
-
sqly - execute SQL against CSV / JSON with shell
Apparently, there were many who thought the same thing; Tools to execute SQL against CSV were trdsql, q, csvq, TextQL. They were highly functional, hoewver, had many options and no input completion. I found it just a little difficult to use.
-
Q – Run SQL Directly on CSV or TSV Files
Reminds me of the textQL extension that's available in Asciidoc.
Point it to an external CSV file, enable TextQL, and bam, there's your query returned as a table. Handy for parts lists, inventory, that kind of crap.
https://github.com/dinedal/textql
https://gist.github.com/mojavelinux/8856117
-
Beginner interested in learning SQL. Have a few question that I wasn’t able to find on google.
Through more magic, you COULD of course use stuff like Spark, or easier with programs like TextQL, sq, OctoSQL.
-
textql VS trdsql - a user suggested alternative
2 projects | 25 Jun 2022
-
Xlite: Query Excel, Open Document spreadsheets (.ods) as SQLite virtual tables
Somewhat-kinda related, the textql extension for Asciidoctor is so dang useful it should be in core.
https://gist.github.com/mojavelinux/8856117
I use this as a "centralized parts repository" for big ol' maintenance manuals. Refresh from PDM/PLM/LSA/Whatever. Rebuild for new parts data.
Built on TextQL, natch
https://github.com/dinedal/textql
go-duckdb
-
Embeddable Database for Go which have Date/Time type
DuckDB also has date functions and Go bindings
-
Range Joins in DuckDB
I've been beating my head trying to get duckdb to statically link into a Go program (I'm neither an expert with cgo nor ld). If anyone else has been able to do this I'd love to see your build steps.
https://github.com/marcboeker/go-duckdb produces a non-static binary by default.
-
Friendlier SQL with DuckDB
Here is a solved Github Issue related to CGO for the Go bindings! If you have another issue, please feel free to post it on their Github page!
https://github.com/marcboeker/go-duckdb/issues/4
-
Dsq: Commandline tool for running SQL queries against JSON, CSV, Parquet, etc.
Yeah frankly the q benchmark isn't the best even though dsq compares favorably in it. It isn't well documented and exercises a very limited amount of functionality and isn't very rigorous from what I can see. That said, the caching q does is likely very solid (and not something dsq does).
The biggest risk I think with octosql (and cube2222 is here somewhere to disagree with me if I'm wrong) is that they have their own entire SQL engine whereas textql, q and dsq use SQLite. But q is also in Python whereas textql, octosql, and dsq are in Go.
In the next few weeks I'll be posting some benchmarks that I hope are a little fairer (or at least well-documented and reproducible). Though of course it would be appropriate to have independent benchmarks too since I now have a dog in the fight.
On a tangent, once the go-duckdb binding [0] matures I'd love to offer duckdb as an alternative engine flag within dsq (and DataStation). Would be neat to see.
[0] https://github.com/marcboeker/go-duckdb
What are some alternatives?
q - q - Run SQL directly on delimited files and multi-file sqlite databases
dsq - Commandline tool for running SQL queries against JSON, CSV, Excel, Parquet, and more.
octosql - OctoSQL is a query tool that allows you to join, analyse and transform data from multiple databases and file formats using SQL.
roapi - Create full-fledged APIs for slowly moving datasets without writing a single line of code.
cq - Query CSVs using SQL
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js. [Moved to: https://github.com/WiseLibs/better-sqlite3]
postgres_scanner
brackit - Query processor with proven optimizations, ready to use for your JSON store to query semi-structured data with JSONiq. Can also be used as an ad-hoc in-memory query processor.
sqlite-utils - Python CLI utility and library for manipulating SQLite databases
sqlite_scanner - DuckDB extension to read and write to SQLite databases