3 ms·
i'm excited about duckdb and have used it for a few "what-if?" projects here and there but keep getting bitten by the file version breaking changes. i appreciat
by swasheck 3y ago
i'm excited about duckdb and have used it for a few "what-if?" projects here and there but keep getting bitten by the file version breaking changes. i appreciate that it's under rapid development and that there's a way to export and import to mitigate it. excited for when that portion stabilizes a bit so that i can roll out some of those prototypes in a more formal and meaningful way for my team
- lnkuiper 3y agoStabilizing storage is high priority for us! You won’t notice anything new while using DuckDB, but we’ve actually rewritten our entire serialization framework in this release. This was a big step towards stable storage
- zX41ZdbW 3y agoI recommend using ClickHouse instead of DuckDB. It has been around since 2016, and it covers and extends the feature set of DuckDB with a huge margin. Worth noting that it never has breaking changes in its table format MergeTree. I'm tracking the progress of DuckDB and see that it is modeled after ClickHouse, but does not approach it in terms of feature completeness, stability, or performance. The closest to DuckDB option is to use its self-contained version, clickhouse-local: https://clickhouse.com/blog/extracting-converting-querying-local-files-with-sql-clickhouse-local https://clickhouse.com/blog/extracting-converting-querying-l... or an embedded version, chdb: https://github.com/chdb-io/chdb https://github.com/chdb-io/chdb
- vgt 3y agoYou should really get into a habit of disclosing your biases, as you seem to make an appearance in every DuckDB related thread with the same comments:) (Head of Produck and Co-founder at MotherDuck)
- zX41ZdbW 3y agoThank you! The topic interests to me, and I usually don't hesitate to comment. PS. I'm the developer of ClickHouse and CTO at ClickHouse Inc.