Earlier quoted context omitted.
Not sheep, lamb.
TIL sheep != lamb
Sheep is a superset of lamb. Lamb is a subset of sheep.
So it is correct to say sheep ≠ lamb, or at least sheep !== lamb.
We will no longer be actively supporting KuzuDB
61–68 of 68 posts
Re: We will no longer be actively supporting KuzuDB
#62Earlier quoted context omitted.
SurrealDB: https://surrealdb.com/
“Cloud native” - not embedded
Correction: there is an embedded mode. https://surrealdb.com/docs/surrealdb/embedding
Re: We will no longer be actively supporting KuzuDB
#63Link to kuzudb internals: https://kuzudb.com/docs/developer-guide/database-internal/
Note that the repo mentions "some of our resources are moving from our website to GitHub: "Docs: http://kuzudb.github.io/docs , Blog: http://kuzudb.github.io/blog " but those links currently redirect to kuzudb.com. I presume they won't be covering the domain name costs in the future and that the transition is in-progress.
They already took it down, unfortunately.
Re: We will no longer be actively supporting KuzuDB
#64Oh too bad. Small fast embedded graph DBs are rare. Any good alternatives?
Another potential one: new and not ready for primetime yet, but from the Lance team so it's promising: https://github.com/lancedb/lance-graph
Re: We will no longer be actively supporting KuzuDB
#65Earlier quoted context omitted.
Note that the repo mentions "some of our resources are moving from our website to GitHub: "Docs: http://kuzudb.github.io/docs , Blog: http://kuzudb.github.io/blog " but those links currently redirect to kuzudb.com. I presume they won't be covering the domain name costs in the future and that the transition is in-progress.
They already took it down, unfortunately.
It is up on the github pages site/domain. At least it was a smooth transition.
Re: We will no longer be actively supporting KuzuDB
#66https://duckdb.org/community_extensions/extensions/duckpgq.h...
PGQ requires you to write using SQL and read using a graph query language. GQL is a standalone language that supports reads/writes. But much of the community is still using cypher. More on this here: https://adsharma.github.io/beating-the-CAP-theorem-for-graph...
The code to implement this was open sourced today:
Re: We will no longer be actively supporting KuzuDB
#67Earlier quoted context omitted.
Note that the repo mentions "some of our resources are moving from our website to GitHub: "Docs: http://kuzudb.github.io/docs , Blog: http://kuzudb.github.io/blog " but those links currently redirect to kuzudb.com. I presume they won't be covering the domain name costs in the future and that the transition is in-progress.
They already took it down, unfortunately.
This URL works for now: https://kuzudb.github.io/docs/developer-guide/database-inter...
Re: We will no longer be actively supporting KuzuDB
#68Oh too bad. Small fast embedded graph DBs are rare. Any good alternatives?
Oxigraph[1] is an option, though it's RDF/SPARQL-based rather than property graph/cypher