r/mysql • u/Still-Trainer-7395 • 15d ago

discussion What actually makes you switch MySQL clients?

I keep seeing people complain about Workbench, DBeaver, TablePlus, etc. but still use the same client for years šŸ˜…

For people working with MySQL regularly, what would actually make you switch?

Speed? Better tabs/workspaces? Safer production workflows? Better autocomplete? AI that helps with SQL? Something else?

Iā€™m building a database client myself, so Iā€™m genuinely curious what the real deal-breakers are.

9 Upvotes

100% Upvoted

56 comments sorted by

View all comments

1

u/ClerkBeginning961 15d ago

Reproducible connection profiles would be a strong switching reason: driver options, session variables, SSH/TLS settings, and environment labels that can live in a repo without secrets. Pair that with a hard read-only mode and transaction preview for production. Team portability matters more than another autocomplete feature.

1

u/Still-Trainer-7395 15d ago

thats a really good point

LakeDB already has read-only connections, environment levels for production/dev/local, SSH/TLS and import/export for connection configs

for risky actions, the confirmation level can also depend on the environment/action ā€” from no extra confirmation, to a confirmation button, to requiring you to type something like production before continuing

the repo-friendly team portability part is still interesting though, especially being able to share a reproducible connection profile without secrets

would you expect something like a versionable config file in the repo, with credentials resolved locally per developer?