The Neon Postgres rows nobody wants to work through
Hand a companion the outcome. It reads the Neon Postgres rows, does the 7-operation version of the job, and stops for your click on anything that changes a record.
Open the row. Check it against something else. Write the change. Move to the next one. That is the Neon Postgres afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a row until you approve it.
What it can do is exactly what Neon Postgres exposes to an account you authorise and nothing beyond it: 7 operations, 2 reads and 5 writes. In practice that means it can upsert a row, update a row and insert a row, and work across the rows and sql queries.
The Neon Postgres API stops at Neon Postgres. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the rows come from?
2 of the 7 operations are reads.
Your account, not a guess at it: a companion can find a row and find row with custom query, and the full list below is the whole list, with nothing inferred from Neon Postgres's documentation.
The rows are what most of this inventory is about, alongside the sql queries. A companion can hold all 7 of these operations and forty open tabs in the same pass, which is how an afternoon of Neon Postgres admin becomes a queue you review.
- Find Row
- Find Row With Custom Query
Who signs off on a new sql query?
All 5 write operations wait for you.
A companion can upsert a row, update a row and insert a row, and each one is staged on an approval card first: you see the row, the field and the new value before it lands in Neon Postgres.
Nothing in Neon Postgres is sent, changed or deleted on your behalf without that click, and a rejected card leaves the row exactly as it was. The gate is the same one on every surface, described at security.
- Upsert Row
- Update Row
- Insert Row
- Execute SQL Query
- Delete Row(s)
What does the recurring rows pass look like?
Yes.
Saved as a routine, the Neon Postgres rows pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The research and analysis playbook catalogues the other recurring shapes of the queries, the Neon Postgres rows sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents