Overview
As an outcome of #53 and migrating to Turso / SQLite, for local development a SQLite file was generated and committed to the repository which should now at least support #46 without the need to provide any direct access to the database.
However, although tables can be edited directly in Turso's UI, or locally using Prisma studio against the .db file, one thing we did lose was was PlanetScales branching feature and nice workflow for doing migrations and data mutations.
Outcomes
- Confirm if Turso has a branching like feature, as was available in PlanetScale
- Figure out if there's a nice way to edit locally, but push remotely
- Document in the README
Overview
As an outcome of #53 and migrating to Turso / SQLite, for local development a SQLite file was generated and committed to the repository which should now at least support #46 without the need to provide any direct access to the database.
However, although tables can be edited directly in Turso's UI, or locally using Prisma studio against the .db file, one thing we did lose was was PlanetScales branching feature and nice workflow for doing migrations and data mutations.
Outcomes