DuckDB 0.7.0

#1

Post by rolandm » Mon, Feb 13, 2023, 9:06 AM UTC

Re: DuckDB 0.7.0

#2

Post by eliasmacpherson » Mon, Feb 13, 2023, 9:45 AM UTC

So say I wanted to try out a workload on various sql databases, mariadb, sqllite, postgres - is there a database that will act as a front end to them?

I find this 'support for pluggable database engines' intriguing. Not least because I can then claim to have used all of the database engines in anger :-)

(I know that it is probably a dumb question due to the following, but I asked anyway: https://en.wikipedia.org/wiki/SQL#Interoperability_and_stand...)

Re: DuckDB 0.7.0

#3

Post by krishadi » Mon, Feb 13, 2023, 9:51 AM UTC

Is duckdb-wasm also going to get this update soon?

Re: DuckDB 0.7.0

#4

Post by hfmuehleisen » Mon, Feb 13, 2023, 9:51 AM UTC

krishadi wrote: post #3

Is duckdb-wasm also going to get this update soon?

Yes we are working on it

Re: DuckDB 0.7.0

#5

Post by smt88 » Mon, Feb 13, 2023, 9:59 AM UTC

This is an interesting niche. Can anyone explain what they're using it for currently?

Much like Redis, I admire the technology but can't think of a project I've worked on that would benefit from it.

Is it for games, maybe? Desktop or mobile apps?

Re: DuckDB 0.7.0

#6

Post by natrys » Mon, Feb 13, 2023, 10:00 AM UTC

Upsert support and Lateral Join are really cool additions, thanks a lot for these. My code became quite ugly without these.

Re: DuckDB 0.7.0

#7

Post by isoprophlex » Mon, Feb 13, 2023, 10:02 AM UTC

> After this release DuckDB will also be able to write hive-partitioned data using the PARTITION_BY clause. These files can be exported locally or remotely to S3 compatible storage.

Kudos to the team for their consistently useful, interesting work. They really seem to know their audience well, to have a well-thought-out feature roadmap.

Makes you wonder if a single, well-specced box running DuckDB is going to be 2024's databricks killer.

Re: DuckDB 0.7.0

#8

Post by Gasp0de » Mon, Feb 13, 2023, 10:03 AM UTC

eliasmacpherson wrote: post #2

So say I wanted to try out a workload on various sql databases, mariadb, sqllite, postgres - is there a database that will act as a front end to them? I find this 'support for pluggable database engines' intriguing. Not least because I can then claim to have used all of the database engines in anger :-) (I know that it is probably a dumb question due to the following, but I asked anyway: https://en.wikipedia.org/wiki…

Just use an ORM? If you code your workload in Python with SQLAlchemy you can just swap out any (relational) db. If you want to do benchmarking or something, this might not be the best approach, since each db might need some specific tuning to reach full potential.

Re: DuckDB 0.7.0

#9

Post by 0x008 » Mon, Feb 13, 2023, 10:05 AM UTC

> DuckDB is an in-process SQL OLAP database management system

I don’t understand what it means. Can someone explain? I don’t get why they put such a complicated claim with unexplained acronyms on their homepage.

When I shop for a db, when should I consider duck DB compared to for example Postgres or MySQL? Or do they compete with arrow or parquet? To me it’s unclear because they don’t say what they compete against.

Re: DuckDB 0.7.0

#10

Post by ddorian43 » Mon, Feb 13, 2023, 10:07 AM UTC

0x008 wrote: post #9

> DuckDB is an in-process SQL OLAP database management system I don’t understand what it means. Can someone explain? I don’t get why they put such a complicated claim with unexplained acronyms on their homepage. When I shop for a db, when should I consider duck DB compared to for example Postgres or MySQL? Or do they compete with arrow or parquet? To me it’s unclear because they don’t say what they compete against.

> I don’t understand what it means.

It's like Sqlite(OLTP) but for OLAP.