search

cwida / duckpgq-extension

DuckDB extension that adds support for SQL/PGQ
https://duckpgq.notion.site/b8ac652667964f958bfada1c3e53f1bb?v=3b47a8d44bdf4e0c8b503bf23f1b76f2
MIT License
73 stars 7 forks source link

Make property graphs persistent #156

Closed Dtenwolde closed 5 days ago

Dtenwolde commented 5 days ago

Fixes #97

Property graphs are now persistent rather than transient. When a connection registers a property graph, it’s stored in the __duckpgq_internal table (I’m betting people won’t use this table name, though future me might regret it!). Any new connection will automatically register all property graphs stored in __duckpgq_internal. Additionally, dropping a property graph now removes it across all connections.

dbeatty10 commented 5 days ago

Thank you for adding this @Dtenwolde 🎉

Stoked to try this out.

Dtenwolde commented 5 days ago

Thanks for the suggestion! I finally got around to fixing your issue :) Let me know if you find other issues (possibly related to this one!)

Dtenwolde commented 5 days ago

@dbeatty10 Out of curiousity, do you use the community edition of the extension or load it the "old fashioned way" with the -unsigned flag and setting the repository endpoint? I am wondering whether it is worth it to update the community extension version to include this PR

dbeatty10 commented 5 days ago

I was using the "old fashioned way", but I've switched to using the community edition of the extension:

INSTALL duckpgq FROM community;
LOAD duckpgq;
Dtenwolde commented 5 days ago

That makes sense, the ability to load from community is a nice addition. I'll fix some more bugs and probably submit the new version somewhere next week then. Thanks!