I don’t understand why the graph – relational crossover ecosystem doesn’t get more love like this – sometimes I want to explore a different paradigm on my data without installing a completely separate database and performing a migration.<p>This is super cool!

If you like kuzudb check out <a href="https:&#x2F;&#x2F;github.com&#x2F;LadybugDB&#x2F;ladybug" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;LadybugDB&#x2F;ladybug</a>

kuzudb was sunsetted.  I think for graph workloads duckdb is best bet, even though this is just a community plugin the upstream duckdb has really robust community doing a lot of heavy lifting and updates.

how&#x27;s this comparable to kuzudb &amp; maybe falkordb ?

SQL&#x2F;PGQ (Property Graph Queries) is part of the SQL standard as of 2023.  I found this project months ago _because_ they included PGQ in their name, I was searching for PGQ implementations.

Maybe I’m just silly, but one suggestion – I thought the PG stood for Postgres at first – some sort of cute name might be in order so people don’t get the impression that they have to install this on Postgres + pgduck or something.<p>LillipadsDB?