Kuzu V0 136 Fixed |link| -

Headline: Smoother Graphs, Faster Queries: Kuzu Patch Highlights

For the curious engineer, here is the distilled diff that defines the fix: kuzu v0 136 fixed

The only lingering criticism is the lack of a rolling release model—users want smaller, more frequent fixes rather than waiting for a monolithic “v0.136 fixed” bundle. The maintainers have acknowledged this and plan to shift to a bi-weekly cadence starting in v0.137. These fixes reinforce that "plug-and-play" nature

A critical patch resolves a rare but disruptive edge case where the system checkpoint failed during specific rollback patterns. EXPORT DATABASE 'path/to/backup_directory' (FORMAT=PARQUET)

EXPORT DATABASE 'path/to/backup_directory' (FORMAT=PARQUET); Use code with caution. Step 2: Update the Dependency Library

Beyond just bug fixes, v0.1.3.6 continues to uphold Kuzu's reputation for speed. As an in-process graph database, Kuzu is designed to be embedded directly into applications, similar to how SQLite works for relational data. These fixes reinforce that "plug-and-play" nature, allowing developers to upgrade their dependencies without fearing breaking changes in their existing query logic.

One of the most significant fixes in this version involves memory pressure during large-scale data ingestion. Users previously reported occasional OOM (Out of Memory) errors when importing massive CSV or Parquet files into a graph schema.