Query parameters, fixed because someone told us
Write WHERE id = :id, type 42, press Run. SQLly now fills in :name, ? and $1 placeholders on every engine, because one user told us it was broken.
On November 10 we sent a free lifetime license to @Pinchez25, who in September asked Chat2DB for interactive query parameters: write WHERE id = :id once, get asked for the value when you run, and never edit the SQL to try the next id. We told him SQLly didn't do that yet and that it was on our list. He downloaded SQLly anyway, said nice things about how fast it feels, and then did the useful thing. He ran the query that brought us into contact in the first place, against his MariaDB:
SELECT *
FROM beneficiaries
WHERE id = :id;
MariaDB answered with a syntax error near :id. Positional ? failed the same way. He wrote back to tell us, politely, with the exact query and the exact error, and pointed out that the placeholder was going to the server untouched.
Our first version didn't work the way it was supposed to
We had shipped a parameter strip months ago, and it does real work: typed inputs, validation, defaults, values that survive a restart. But it only woke up when you declared a parameter with a special -- sqlly param: comment. Nobody writes that. People write :id, or ?, or $1, because that is what every driver, ORM and stack trace has taught them. So the feature existed, and for the query people actually type it did nothing. SQLly sent :id straight to the server.
It was worse than that. While testing the fix we found that SQLly's own formatter, set to MySQL or SQL Server, turned id=:id into id =: id. That no longer runs anywhere. It is the same bug the Chat2DB maintainers listed in their design for this feature, and we had it too.
What it does now
Write a placeholder and the strip opens with an input for it. Type a value, press Run, and the query goes out with the value filled in. Your script never changes.

- Named, positional and numbered.
:nameon every engine,?everywhere except PostgreSQL (where?is a JSON operator), SQLite's?3, PostgreSQL / DuckDB$1, and on SQL Server any@namethe script doesn'tDECLAREitself. A name used twice is one input. - Values read the way you mean them.
42is a number,trueandNULLare what they say, anything else is text, and'42'in quotes forces text. A zip code like007stays text. Every value is escaped for your engine, so a quote or a backslash in it is only ever data. On PostgreSQL values go in untyped, soint_col = :idandtext_col = :idboth work. - Only what you run needs a value. Fill in placeholders for the whole script ahead of time, or don't. When you run one statement, only its placeholders are required. If one is empty, nothing is sent, its row says required, and the cursor jumps into it.
- No false alarms. Beekeeper users have complained about clients asking for parameters nobody declared, and we didn't want to swap one annoyance for another. Strings, comments, quoted names,
$$function bodies,::casts, array slices, JSON paths, MySQL's:=and labels, sqlcmd lines and Oracle's:neware all left alone. - Explain uses the same values, the values stay with the tab across restarts and windows, named placeholders remember recent values as one-click chips, and
-- sqlly param: :since date = 2026-01-01still gives a placeholder a type and a default when you want one.

:client_id and :status.
@top is declared so it stays a variable; the undeclared @Country gets the input.The formatter fix shipped too: placeholders stay whole on every dialect, and x=? formats as x = ?. If you would rather nothing asked for values, the switch is in Settings ▸ Editor ▸ General ▸ Query parameters. The Query parameters docs have the details.
Tell us when we suck
This got fixed because one person tried the thing we said we'd do, saw it fall over, and took five minutes to tell us exactly how. He could have shrugged and gone back to editing 42 to 43 by hand. A report like his is the most useful thing anyone can send us. It's specific, it's honest, and it came with the query.
So thank you, @Pinchez25. And to everyone else: if SQLly does something dumb, slow, ugly or wrong, please tell us. Help ▸ Send Feedback in the app, or just reply to any email from us. The reports that sting a little are usually the ones that make the biggest difference.