PlanetScale

PlanetScale manages logins in its dashboard, so you create a read-only one there. Rowsend’s setup SQL only creates a view. In Rowsend, PlanetScale appears twice in the connect dialog, once under Postgres and once under MySQL. Pick the one your database uses.

Postgres

1. In PlanetScale, open your database, click Connect and pick the branch.
2. Create a role. Untick pg_write_all_data so only pg_read_all_data is left.
3. Copy the connection URI.

MySQL

1. In PlanetScale, open your database, click Connect and pick the branch.
2. Create a password. Keep Primary and set the role to Read-only.
3. Under Connect with, choose Prisma and copy the DATABASE_URL value.

Connect

1. In Rowsend, open Contacts, click Connect a database, choose PlanetScale under your engine, paste the connection string and click Continue.
2. Choose what Rowsend reads: a table, its email and last-changed columns, and any extra columns. The select must return id, email and updated_at.
3. Click Copy SQL and run it in PlanetScale’s console. On Postgres it creates a rowsend schema with a contacts view and lets your role read it. On MySQL it creates a rowsend_contacts view in your database. It creates no login.
4. Click Test and connect.

Before connecting, Rowsend checks that the login can’t write and refuses one that can. On MySQL, PlanetScale enforces password roles outside MySQL’s grants, so Rowsend tries an update that matches no rows and expects PlanetScale to deny it. Nothing changes either way.

Rowsend saves this login on your computer, encrypted with your system keychain.