Project moved to github.com/duckdb/duckdb-go (v2.5.0+)

[mlafeldt]

Important

This project has moved to github.com/duckdb/duckdb-go starting with v2.5.0.

To migrate: Update your import paths from github.com/marcboeker/go-duckdb to github.com/duckdb/duckdb-go.
→ Full migration guide

Issues and PRs

Please use the new repository at https://github.com/duckdb/duckdb-go for all new issues and pull requests.

We will migrate valid existing issues to the new repository. Please do not create duplicate issues.

---

Background

Over the last few years, the Go client has become a primary DuckDB client. We'd like to thank Marc Boeker for all his work on creating this driver and implementing the various interfaces of the database/sql package! We'd also like to thank all the other external contributors for their various PRs and other contributions.

With the driver being a primary DuckDB client, over the last years, the DuckDB team has gradually increased its involvement in the maintenance of the driver, to guarantee that it is constantly updated and that critical bugs (e.g., crashes) are fixed. Now we have a Long-Term Support release, so starting from early next year, we will have two releases in parallel (v1.4 LTS and v1.5). Additionally, more DuckDB customers use and rely on the Go client, which necessitates prioritization of certain features from us.

These points all add to the maintenance work, which the DuckDB team is happy to perform! However, the motivation behind this fork, which is a joint effort of Marc Boeker and the DuckDB team, is to fully transfer the maintenance and day-to-day work of the driver to the DuckDB team. That being said, the DuckDB Go client has become what it is also due to its many contributions from the community, and we are looking forward to your future PRs, issues, and discussions!

The license is unchanged: the migrated repository keeps the original MIT license, which is the same for core DuckDB and other primary clients.

[derekperkins]

Why fork it there vs moving the existing repo?

[taniabogatsch]

Hi @derekperkins! Indeed, we initially wanted to move the repository. However, when moving a mock-module ourselves, we found that a repository transfer + GitHub's automatic redirect would work to some degree, but that it would break module path validation. See also https://groups.google.com/g/golang-nuts/c/Yjk5xrRnAnc.

EDIT: In hindsight, it probably would've worked to move the repo and then fork the moved repo back to marcboeker/go-duckdb. But Marc ending up with an "empty" fork also does not feel right, after having implemented most of the original driver.