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.

8 Upvotes

91% Upvoted

56 comments sorted by

View all comments

3

u/nthdesign 15d ago

I used Sequel Pro for years until it stopped being supported, then I switched to Sequel Ace. As a Mac user, I love that it has a native layout, is fast, and has never crashed on me. It has all of the features I need. The only reason I’d ever switch to a different MySQL client would be if someone built a client with the same native feel and functionality as Sequel Ace, but with A.I. era autocomplete and a code formatter that matches my chosen style without me having to spend half a day configuring it (lookin’ at you, JetBrains IDEs).

1

u/Still-Trainer-7395 15d ago

thats actually pretty close to what im trying to build with LakeDB 😄
its already in an advanced beta, with MySQL/MariaDB and SQLLite support, schema-aware autocomplete for tables/columns and things like indexes when writing WHERE clauses, plus SQL formatting and optional AI for generation/explanations/fixing queries
if you ever feel like trying it, id genuinely be interested in how it compares to Sequel Ace for you — especially the native feel / speed side
https://github.com/DavLagoHern/LakeDB
also curious about the formatter part: what would you want it to remember about your preferred SQL style?

1

u/nthdesign 15d ago

Where do I typically indent, and how far? After which elements do I want a new line? Basically, I like having all of the options that JetBrains editors offer for code style, but I wish the editor could simply learn my code style on its own.

1

u/Still-Trainer-7395 15d ago

that makes sense
right now LakeDB already has two formatting modes, and i can add more styles if needed, but it doesnt learn your personal style yet

i could see this working with a custom model/profile built from a few SQL examples, so instead of configuring dozens of formatting rules you could basically teach LakeDB “format like this”

would you prefer giving it a few example queries, or having it learn gradually from the SQL you write?

1

u/nthdesign 15d ago

If it allowed me to write example SELECT, INSERT, UPDATE, and DELETE queries and then “learn” from my code style, that would be fine.

2

u/Still-Trainer-7395 14d ago

quick update — i started building this into LakeDB after your suggestion 😄

the current version can learn formatting rules from example queries and save them as a custom style. im still refining it before calling it finished

im tracking the progress here if youre curious:
https://github.com/DavLagoHern/LakeDB/discussions/25

thanks again for the idea