Live data from Hacker News

DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

duckdb.org

71–80 of 167 posts

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#73
post #47

I really wish ALL software project / framework / libary could follow the lead here. Instead of your marketing page telling me how world changing awesome tech you have, which really is a consumer marketing strategy. Just do it like DuckDB, When to use DuckDB ; When to not use DuckDB

I couldn't put my finger on why I felt like I had just read something useful, but that's it: clear, concise and straight-forward information to help you evaluate use.

Only thing wrong I saw was the detection of the platform. It detected my linux box as "Unix" and proposed I download OSX libs.

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#74

Earlier quoted context omitted.

One of the authors here - portability of the storage is indeed one of our goals. We test that the same file can be loaded everywhere on different systems, including between ARM and x86. I should mention the storage is still very much a work-in-progress. We are actively working on redesigning the storage to add compression and other extra features, meaning the storage format can change and be incompatible between diff…

Couldn't you have used an already existing format for storage, e.g. Apache ORC?

Those formats have a different use case from a database system - they are mostly designed for write once, read many times workloads. As far as I’m aware you cannot update them in an ACID compliant manner, for example, which makes it difficult to use them as backend for an ACID database system.

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#76
Can someone recommend whats the best way to connect to a memory DuckDB instance from php(php_fpm) and get return in usable format?

E.g. would be used for offline statistical analysis

Alterntively, any way to export cli sql results as csv?

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#77
post #47

I really wish ALL software project / framework / libary could follow the lead here. Instead of your marketing page telling me how world changing awesome tech you have, which really is a consumer marketing strategy. Just do it like DuckDB, When to use DuckDB ; When to not use DuckDB

What an excellent point! I suppose the consumer marketing strategy comes from pure imitation - people look around them how "professional" products discuss themselves - with the aim of selling a product and service - and simply copy that.

Algorithms textbooks don't create marketing blurbs for linked lists...

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#78
post #47

I really wish ALL software project / framework / libary could follow the lead here. Instead of your marketing page telling me how world changing awesome tech you have, which really is a consumer marketing strategy. Just do it like DuckDB, When to use DuckDB ; When to not use DuckDB

We should make a list of technology that does this, because I know Clickhouse also has a reasonably detailed page on when to use it and when to not use it and why. Postgres also has a very nice “do and donts” wiki page.

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#79
3-month old HN thread [1] with good information from the authors and others.

“An embeddable column store for data science” (Pandas and dbplyer) would have been a good description at that time but the addition of JDBC/Java support expands the use cases.

[1] https://news.ycombinator.com/item?id=23287278

Re: DuckDB – An embeddable SQL database like SQLite, but supports Postgres features

#80
post #12
post #4

Strict typing has been the one big feature missing from SQLite, that this presumably brings.

Foreign keys enabled by default or by configuration setting would be another big feature missing from SQLite3, but I couldn't find any mention of foreign keys in DuckDB's documentation.

OLAP databases seem to omit ForeignKeys. Redshift does this for example. They don’t exist in BigQuery (but BQ pushes you towards a single table design anyway so moot point I guess).
Post reply on HN