MySQL StrawberryGet the refund rate and the reason behind it
A companion pulls the number, then tells you which of those refunds arrived with a support ticket. It checks all four hundred, not the first twenty.
The orders table has forty million rows and a `status` column with nine values. Three are historical, one is a typo from 2021, and a report still counts it. The query is easy. Knowing which value means the customer actually paid is the job.
A companion works both halves: the query, through an account you connect, then the support threads that explain the number. It does the thirty-first cross-check as carefully as the first.
| A MySQL client | A Strawberry companion | |
|---|---|---|
| Joining a row to a support thread | Copy the id, switch tabs, read | Both in one pass, written up |
| Repeating the same six numbers weekly | You remember, or you don’t | A routine you review |
| Guarding against a destructive statement | Your GRANTs | Your GRANTs, plus the action switched off |
| Knowing what status = 7 means | In your head | In the glossary you hand it, then in every answer |
| Turning the result into something finance can read | Copy, paste, retype | Drafted with the query shown beside it |
Read the tool list before you write the prompt
The MySQL entry under `strawberry://settings/integrations` has an Available tools list: every tool the app exposes, with the read-only ones marked. That list is the contract, and it is the only place the contract is current.
Then set each action in the Permissions block: Ask every time, Always allow, or off. For a reporting query against a replica, Always allow is defensible. For anything that writes, it usually is not.
What does a scoped MySQL user look like?
Boring.
`CREATE USER` with a password nobody has in a shell history, `GRANT SELECT ON reporting.*`, no `GRANT ALL`, no root, and a host restriction if your topology allows one. If you run a replica, connect to the replica.
Two settings earn their keep. `max_execution_time` caps a SELECT so a thinking-out-loud query dies on its own. `MAX_USER_CONNECTIONS` stops a retry loop eating the connection pool. Both are what you would set up for a new BI tool.
- A dedicated user with SELECT on the specific schemas, granted per schema rather than globally.
- A replica endpoint if one exists, so read load stays off the primary.
- `max_execution_time` and `MAX_USER_CONNECTIONS` set on the account.
- Write privileges only where a named workflow needs them, and the rest switched off.
Why not just use a MySQL client?
Because most questions that start in MySQL do not end there.
A refund rate is a number until somebody asks which of those refunds came with a support ticket. A companion holding the database connection and your signed-in support tool does that cross-reference and writes it up.
The other case is repetition. The same six numbers, every Monday, in the same shape, delivered as a short note. That is weekly reporting. If the numbers feed finance, ai for finance teams is the neighbouring page, and ai for analysts covers the read-heavy version.
Hand it the glossary on day one
The connection handles the credential.
It is stored encrypted, Strawberry never receives it, you see the exact permissions before you approve them, and it is scoped to one Strawberry profile. Disconnect and the managed account is removed.
Your schema is the part you supply. `status = 7` means a chargeback only once somebody says so. Give a companion the glossary and check the first three answers against something you already trust, the way you would with a new hire.
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