22. Inspect local data with Studio

The tutorial chapters run against in-memory SQLite, so nothing survives them. Point Studio at a migrated project database instead. For example, scaffold a project with rent new, add models with rent init User Post Comment, apply them with rent migrate dev --name initial, and then open the resulting rent.db:

rent studio

Choose users, posts, or comments in the sidebar. Studio shows the catalog-derived columns and primary key, then loads the first page of rows. It starts read-only so exploration cannot accidentally change the tutorial data.

To adjust a fixture, stop Studio and opt into editing:

rent studio --allow-writes

Double-click a cell and enter its new value as JSON. For example, a string must include JSON quotes:

"A clearer post title"

Studio sends a parameterized update constrained by the row's full primary key and accepts success only when exactly one row changes. Its automated CLI test exercises catalog browsing, write opt-in, successful editing, and default write rejection on every nextest run.