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.
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.
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.
SQL/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.
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.
This is super cool!
how's this comparable to kuzudb & maybe falkordb ?
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.
If you like kuzudb check out https://github.com/LadybugDB/ladybug
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.
LillipadsDB?
SQL/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.