Live data from Hacker News

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

duckdb.org

81–90 of 167 posts

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

#81
post #6

Earlier quoted context omitted.

Man, I’ve wanted the “compatible SQL engine with only RAM storage” for testing for YEARS. Closest I got was some shenanigans with MSSQL’s LocalDB.

I use docker to spin up new postgresql DBs on the fly

I do that too but it’s a noticeable overhead, I guess it wouldn’t be great for mass-testing scenarios.

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

#82
post #6

Earlier quoted context omitted.

Man, I’ve wanted the “compatible SQL engine with only RAM storage” for testing for YEARS. Closest I got was some shenanigans with MSSQL’s LocalDB.

I use docker to spin up new postgresql DBs on the fly

Same here, and I run the same set of migrations that run in production. To he clear, this is only done once per test session, not for individual tests, and the tests are written in such a way that they don't interfere with each other.

The overhead is actually pretty small, less than 10s. I'd saw too much for unit tests, but we'll within the tolerable range for integration/functional tests. Compared with the time I'd spend hacking together some brittle and unrealistic in-memory alternative, I much prefer to use a real database.

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

#85
Please think twice before choosing an embeddable database for hostable software. I see so many open-source projects that get hampered own the line because they chose sqlite and there's now a SPoF that would require a significant rewrite to eliminate - especially as sqlite depending on configuration either corrupts or becomes extremely slow when stored on distributed/network file systems. I assume this goes for duckdb as well.

Embeddable databases absolutely have legit use-cases, but I see them being used for projects where it'd have saved so much trouble to use a proper ORM (perhaps with sqlite support!) from the beginning.

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

#86

Is this backward compatible with SQLite?

The on-disk format is different it seems. But there is an implementation of the SQLite C API for interacting with the database. So it depends on which level / what purpose you want compatibility.

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

#87
What would be the recommended way to migrate data from SQLite and DuckDB? Should I dump SQL from SQLite and load in DuckDB? Or use Parquet, or CSV export/import? I think those interested in the tagline "like SQLite but more features" might be interested in a quick howto/guide like that.

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

#88
I was discussing with a coworker what would be the best option, embbbedabble or service for a database runnning for a Windows GUI app.

My bet was on embeddable, so SQLite, is that the right choice?

It seeems a nightmarish scenario to have 500 postgres instances running on client machines and being accessible from the internet albeit with security enabled and such...

am i right?

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

#89
post #88

I was discussing with a coworker what would be the best option, embbbedabble or service for a database runnning for a Windows GUI app. My bet was on embeddable, so SQLite, is that the right choice? It seeems a nightmarish scenario to have 500 postgres instances running on client machines and being accessible from the internet albeit with security enabled and such... am i right?

Countless mobile apps use SQLite.

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

#90
post #89
post #88

I was discussing with a coworker what would be the best option, embbbedabble or service for a database runnning for a Windows GUI app. My bet was on embeddable, so SQLite, is that the right choice? It seeems a nightmarish scenario to have 500 postgres instances running on client machines and being accessible from the internet albeit with security enabled and such... am i right?

Countless mobile apps use SQLite.

In this case though I'm talking of a COBOL backend very old windows app.

We want to move data from COBOL files to a database, we're making our own migration tools/scripts in python (In order to mainly rename weird name table/column names to sanish ones), and we can target any SQL flavour/database we want to insert that data at.. the question is what's the better call here...

SQLite seems pretty good enough, at least until we can move our whole app to a more web-friendly environment at which point something like postgres might make more sense? but that could take a couple years... (we're a small team/company in a very specific niche/locale)

Post reply on HN