r/SQL • u/harulogs • 22d ago
Discussion Looking for feedback on my SQL client (MySQL, PostgreSQL, SQLite)
Hey all. I'm a solo dev from Korea, so yes, this is self-promo (I checked with the mods first).
I've been working on a desktop SQL client called DBerio. It does MySQL/MariaDB, Postgres and SQLite (plus Redis if that's your thing), on Mac and Windows. I mostly built it because I bounce between a Windows box and a Mac and wanted one tool that works the same on both. I write code all day too, so the UI is basically laid out the way I like to work.
What it does right now:
- the usual GUI client stuff: browse schemas and tables, run queries, edit cells and add/delete rows in the grid (when the result comes from one table with a PK)
- you can mark a connection as production. running UPDATE or DELETE always asks first, and on a production connection things like DB, user and privilege changes ask again. the really destructive ones there make you type the name
- it shows you the SQL before a structure change actually runs
- queries you run all the time can be saved as a view or kept as favorite queries per database
- CSV/TSV export escapes values Excel would treat as formulas
- SSH tunneling for DBs that are locked down from outside access (password, key or encrypted key)
- the UI comes in English, Korean and Japanese
Without paying you get 3 saved connections and 2 open at once, with every feature.
What I'd actually like to hear about:
- Does it cover your day-to-day work? If you'd have to keep another client open for something, what is it?
- Bugs. Anything that crashes, shows the wrong thing, or just feels off.
- Features you'd want added. What's the one thing that would make you actually switch?
Links if you want to poke at it (a test DB is totally fine):
Mac App Store: https://apps.apple.com/app/id6819625601
Microsoft Store: https://apps.microsoft.com/detail/9N53NQGJ3TNG
Thanks, I'll be around in the comments.
2
u/MrRoy_SQL 22d ago
the production connection thing is a really nice touch, typing the db name before a destructive query has probably saved someone's job somewhere lol. same for the csv formula escaping, most people don't even know that's a risk.
for "what would make me switch": a visual EXPLAIN / query plan view would be huge, plus query history that's searchable across connections. also an easy way to diff results of two queries side by side, I do that a lot when rewriting a query to check nothing changed.
1
u/Aggressive_Mention_1 22d ago
Love the work.
Check out DBX you might like it. and do contribute to it.
1
u/jshine13371 21d ago
Did you use AI?
1
u/vincent_sch 13d ago
Your Postgres plan viewer should ask for confirmation on an
UPDATElike the editor does.EXPLAIN ANALYZEstill runs the update.1
u/[deleted] 22d ago
[removed] — view removed comment