Max Gabrielsson

DuckDB v1.5 で本体に入る GEOMETRY 型のドキュメントができてた。細かいところまで説明してくれて勉強になる duckdb.org/docs/preview/s…

@penberg How do you deal with cross-database dependencies of types? E.g. what happens if i attach database A and B, and then use a custom type stored in A when creating a table in B? What if I detach A after and persist B? Or drop from A after detaching B?

Turso 0.5.0 is now out! ⚡ Concurrent writes is now beta 🔍 Full-text search with Tantivy 🔒 STRICT mode stable + user-defined types Big thanks to the 50+ people who contributed over 3,000 commits into this release! turso.tech/blog/turso-0.5…

day 30 of unemployment

Really... one result???

Today we're launching DuckLake, an integrated data lake and catalog format powered by SQL. DuckLake unlocks next-generation data warehousing where compute is local, consistency central, and storage scales till infinity. ⁠DuckLake is an open standard and we've implemented it in the "ducklake" DuckDB extension. – Read the announcement blog post at duckdb.org/2025/05/27/duc… – Visit the new DuckLake website at ducklake.select

We are brewing something exciting for next week ⏳

More context

Or ducked in general. You're losing so much of the benefits of vectorized execution if you trash the cache with allocator calls - not to mention the contention caused when allocating from different threads.

Here are some interesting profiling results. Having DuckDB executing a large join with the new spatial join operator, it spends about 50% of the time just _deserializing_ and constructing GEOS geometries, 15% just calling GEOS destructors, and just 2% evaluating the predicate 🥲

@yutannihilation Haha no worries, its a very experimental idea but its got me super excited!

@Maxxen_ Oh, sorry for the spoiler! I'm looking forward to seeing the progress👍

@thomasforth @duckdb Yeah at some point we should have a native geojson reader - but its complex since we already have a very advanced general json reader in the json extension, and I don't really know how to provide the same capabilities (eg schema inference) without copying all the code...

@duckdb Step 1 works great. File is reduced in size from 1.3GB to 60MB with no loss of quality that could materially effect the results of the query. Safely throwing away data early is a data science power move and tends to separate good from quite people.

A while back, before I built my "population within a circle for the whole world" tool, I built a "population and the associated density within concentric for anywhere in Great Britain" tool. It's still online it still works. But,... tomforth.co.uk/ringpopulation…

Its happening y'all, DuckDB's spatial joins are about to get good, actually. github.com/duckdb/duckdb-…

DuckDB 1.2.1 is out: github.com/duckdb/duckdb/…

@jpurrutia4 @matsonj me_irl

@matsonj All I want is for this to be the new DuckDB logo

in some ways you could say the future is already here

@zack_overflow Reminds me of the rabbit-hole related to printing floats. "Print a double with the least amount of digits to still round-trip without loss of precision", printf("%g") won't do it, and it turns out be surprisingly hard (and performance expensive).

They literally asked the dude who invented the conservative garbage collector to make a calculator app... And even he couldn't do it alone This is the most insane level of programmer nerd sniping I've ever read

@paolo_pash It's what PROJ gives as the "name" for the projection. Im still undecided on what to use as the display name, but regardless, the actual projection parameters are stored under-the-hood (and is what is used when comparing two geometry types).

@Maxxen_ But 3857 is also based on wgs84. Why did they use such an ambiguous data type description?

Experimenting with CRS tracking support in DuckDB Spatial 🗺️👀

New blog post: Query Engines: Gatekeepers of the Parquet File Format In this post, Laurens Kuiper argues that we are wasting a lot of bits by not using the Parquet format to its full extent – a limitation caused by the lack of support for Parquet features in some systems. duckdb.org/2025/01/22/par…