226 karma · joined April 21, 2021
But it's also stuff like `"SELECT * FROM my_df"` – It's super cool but why is my database connecting to an in-memory pandas data frame? On the other hand, DuckDB can connect to remote Parquet files and interact with them without (explicitly) importing them.
In these examples, DuckDB feels more like an ephemeral SQL-esque Pandas/Polars alternative rather than a database.
Probably it's just me losing track of what a database is and we've evolved from "a monolithic and permanent thing that you store data on and read data from via queries".
When I look at SQLite I see a clear message: a database in a file. I think DuckDb is that, too. But it’s also an analytics engine like Polars, works with other DB engines, supports Parquet, comes with a UI, has two separate warehouse ideas which both deviate from DuckDB‘s core ideas.
Yes, DuckLake and Motherduck are separate entities, but they are still part of the ecosystem.
It will take years until this can be widely used as intended.
Is anyone familiar with something similar for Python in general and Django in particular?
Adding some obscure consumer protection rule is a much less controversial change to the law.
The traditional German legal doctrine sees the enforcement of fair business practices rather in the hands of the authorities than in those of consumers. Of course, there is little evidence of this to work in this or similar contexts.