better-sqlite3
go-duckdb
| better-sqlite3 | go-duckdb | |
|---|---|---|
| 1 | 4 | |
| 3,153 | 496 | |
| - | - | |
| 7.7 | 8.1 | |
| almost 2 years ago | 3 days ago | |
| C++ | 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.
better-sqlite3
-
Range Joins in DuckDB
I tried to replace SQLite with DuckDB for a customized install of better-sqlite3[1] and failed.
[1] https://github.com/JoshuaWise/better-sqlite3
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?
LittleDB - Little Sql like Database for ESP32 boards
dsq - Commandline tool for running SQL queries against JSON, CSV, Excel, Parquet, and more.
simple - 支持中文和拼音的 SQLite fts5 全文搜索扩展 ｜ A SQLite3 fts5 tokenizer which supports Chinese and PinYin
textql - Execute SQL against structured text like CSV or TSV
sqlite3cpp - C++17 Wrapper of SQLite
roapi - Create full-fledged APIs for slowly moving datasets without writing a single line of code.
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
postgres_scanner
q - q - Run SQL directly on delimited files and multi-file sqlite databases
sqlite_scanner - DuckDB extension to read and write to SQLite databases
duckdb - DuckDB is an in-process SQL OLAP Database Management System