Kuzu V0 120 Better !!exclusive!!

"We use centerless grinders for hydraulic piston rods. Our dressing cycles were every 200 parts with Norton. With Kuzu V0 120, we dress every 450 parts. That is mathematically better." —

import kuzu # Initialize an on-disk database and connection db = kuzu.Database("./knowledge_graph") conn = kuzu.Connection(db) # Create a simple schema conn.execute("CREATE NODE TABLE User(id INT64, name STRING, PRIMARY KEY(id))") conn.execute("CREATE NODE TABLE Skill(id INT64, name STRING, PRIMARY KEY(id))") conn.execute("CREATE REL TABLE KNOWS(FROM User TO User)") conn.execute("CREATE REL TABLE HAS_SKILL(FROM User TO Skill)") # Fast data insertion using Cypher conn.execute("CREATE (:User id: 1, name: 'Alice')") conn.execute("CREATE (:User id: 2, name: 'Bob')") conn.execute("CREATE (:Skill id: 101, name: 'GraphRAG')") conn.execute("CREATE (:User id: 1, name: 'Alice')-[:KNOWS]->(:User id: 2, name: 'Bob')") conn.execute("CREATE (:User id: 1, name: 'Alice')-[:HAS_SKILL]->(:Skill id: 101, name: 'GraphRAG')") # Query the graph response = conn.execute( "MATCH (a:User)-[:KNOWS]->(b:User)-[:HAS_SKILL]->(s:Skill) " "RETURN a.name, b.name, s.name" ) while response.has_next(): print(response.get_next()) Use code with caution. 🎯 Ideal Use Cases for v0.12.0 Releases · kuzudb/kuzu - GitHub kuzu v0 120 better

Despite the name change and the team's move to Apple, the database continues as an embedded graph database "We use centerless grinders for hydraulic piston rods

Kùzu v0.12.0: Why the Embedded Graph Database Just Got Better That is mathematically better

We have expanded the function library to make Cypher scripting in Kuzu more expressive.

As always, we're excited to hear from the Kuzu community and encourage you to get involved. Whether you're a user, contributor, or just interested in learning more, we invite you to join our community forum or Slack channel .