nushell-storage

To persist data across Nushell commands without an external database, use stor-backed in-memory SQLite. It provides a lightweight, in-process storage layer that keeps tables accessible throughout interactive sessions and long-running pipelines.

The best way to share state in long-running Nushell pipelines is using a session-scoped SQLite storage layer. This approach allows you to create tables, insert and update records, and query data with SQL across multiple commands.

Yes, you can export in-memory Nushell data to a SQLite file for later reuse. The storage layer supports persisting critical datasets from the session-scoped store directly into standard SQLite files.

Nushell supports SQL operations for session-scoped tables through its stor-backed storage layer. You can create or open tables, insert, update, and delete records, and query data using standard SQL syntax.

You need stor-backed storage in Nushell workflows when performing cross-command analytics or running long-running data pipelines that require shared state. It solves the problem of keeping tables and records accessible without relying on external services.

A limitation of in-memory SQLite for Nushell data persistence is that data is session-scoped and lost when the session ends unless explicitly exported. You must persist critical datasets to SQLite files to ensure long-term durability.