Kuzu V0 136 Fixed __exclusive__ -

Multi-threaded write operations were a nightmare in v0.135. Two threads writing to different segments of the same data structure would occasionally produce torn writes—half of one transaction, half of another. This led to silent data corruption, which is catastrophic for any database or stateful application.

Kùzu continues to position itself as a high-performance, embeddable alternative to server-heavy graph databases. While earlier versions focused on speed, v0.3.6 prioritizes , particularly for developers working on macOS/iOS or those using complex union data types. It remains a top choice for OLAP workloads and machine learning pipelines due to its vectorized query processor and seamless Python integration. Pros: High Performance And Low Overhead Graphs With KuzuDB kuzu v0 136 fixed

A different library entirely (like a specific dataset version for AI). A typo for v0.1.3 or v0.3.6 . Multi-threaded write operations were a nightmare in v0