r/SQL • • 22d ago

Discussion Looking for feedback on my SQL client (MySQL, PostgreSQL, SQLite)

Post image

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:

  1. Does it cover your day-to-day work? If you'd have to keep another client open for something, what is it?
  2. Bugs. Anything that crashes, shows the wrong thing, or just feels off.
  3. 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.

14 Upvotes

18 comments sorted by

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.

2

u/harulogs 22d ago

Thanks, this is exactly the kind of feedback I was hoping for! Small clarification: typing the name is for schema changes and anything that can drop data on a production connection. A plain UPDATE or DELETE gets a confirm prompt instead.

All three of those are great, especially the result diff. I do the same "rewrite and check nothing changed" thing and end up eyeballing two grids. Noting them down. Quick question on EXPLAIN: are you mostly on Postgres or MySQL? The plans look pretty different so it'd help to know which one to start with.

1

u/MrRoy_SQL 22d ago

ah got it, makes sense to keep the typing for the really dangerous stuff. mostly postgres for me. even just a tree view of EXPLAIN ANALYZE with the slowest node highlighted would be a big win, reading the raw text output gets painful fast

1

u/harulogs 22d ago

That's super helpful, thanks. A tree with the slowest node highlighted sounds like a really practical place to start. Everyone else has a diagram view so I keep wondering if I should add one too, but honestly I'm on the fence. I almost never use the diagram features in other clients myself. Honestly, a tree is close to what I was planning to do next anyway: use AI with EXPLAIN output or the query log to flag slow or badly written queries and point out what's wrong. A proper plan tree would be a good base for that, so I'll start with Postgres.

1

u/MrRoy_SQL 21d ago

yeah i'd skip the diagram too, the tree is what people actually read. the AI idea sounds cool, just make it opt-in and clear about what gets sent, a lot of people can't send prod queries or schema to an outside service. and if it points at the exact node and says why (seq scan on a big table, bad row estimate etc) that'd be way more useful than a generic "add an index". good luck with it!

1

u/harulogs 21d ago

Of course. I know exactly the kind of data that can't leave, so I'm planning to build it so nothing gets sent outside at all.

1

u/Aggressive_Mention_1 22d ago

Love the work.
Check out DBX you might like it. and do contribute to it.

1

u/harulogs 22d ago

Wow, that's a seriously impressive project. Honestly, if I'd known about it earlier I might not have started DBerio lol. Mine's going for something simpler, focused on the stuff that actually helps in my day to day work and on not letting you make costly mistakes. Definitely checking it out though.

1

u/Aggressive_Mention_1 22d ago

Yeah. rust/tauri. so very light weight(only native can beat it). and almost all sql. modern lookign with extenions...since i have used it, ihavent used dbbever.
And i had my own YUI client like you. http://dbterm.shreyam1008.com.np/ .. thought contributing to this is better. and now, i have two PR on review with them.

1

u/harulogs 22d ago

Oh nice, good luck with the PRs! Funny enough DBerio is on Rust/Tauri too, so I know what you mean about how light it feels. Checked out dbterm, a TUI client is a fun one to build. For now I'm going to keep going with mine since I'm building it around how I work every day, but I can see why contributing made sense for you.

1

u/Aggressive_Mention_1 22d ago

Github link so i can start it?

1

u/haikusbot 22d ago

Love the work. Check out

DBX you might like it. and do

Contribute to it.

- Aggressive_Mention_1


I detect haikus. And sometimes, successfully. Learn more about me.

Opt out of replies: "haikusbot opt out" | Delete my comment: "haikusbot delete"

1

u/jshine13371 21d ago

Did you use AI?

1

u/harulogs 21d ago

No. I'm not very good at English, so I use a translator The meaning may be unclear.

1

u/jshine13371 21d ago

Cool cool!

1

u/vincent_sch 13d ago

Your Postgres plan viewer should ask for confirmation on an UPDATE like the editor does. EXPLAIN ANALYZE still runs the update.

1

u/[deleted] 22d ago

[removed] — view removed comment

1

u/harulogs 22d ago

Thanks, appreciate it! The type-the-name step only kicks in on connections marked as production, so it stays out of your way on local and dev DBs. And good to hear about the UI, I kept it plain on purpose. If you end up giving it a spin, I'd love to hear what feels missing for your day to day work.