I've been working with MySQL for my web projects and got really tired of constantly switching between different clients, each with its own issues. Some clients are just too bloated, some feel overly generic, and others don't quite fit into my everyday MySQL workflow. So, I decided to start building my own open-source MySQL client that aims for fast query execution, clean schema browsing, a simple user experience, and no unnecessary clutter. It's still in development, but I'm focusing on enhancing MySQL support and making the experience as smooth as possible. For those who use MySQL regularly, I'd love to know: what's the most annoying thing you encounter with your current database client? If you're interested in checking it out, here's the repo: https://github.com/debba/tabularis
5 Answers
Are there any plans for a browser-based version?
I really appreciate the streamlined focus on MySQL. One major nuisance I encounter is query results that cut off long text without an easy way to expand them. Keep working on that!
Absolutely, we're just getting started and are looking to add features like that!
This project sounds great! I totally get the frustration with MySQL tools. One big issue for me is how sluggish the clients can get when browsing schemas to locate tables. I’ll check out your repo; best of luck with everything!
Thanks! It's still in beta, and I’m trying to improve it regularly. Contributions are always welcome!
I totally resonate with your experience! I've switched between Sequel Pro, TablePlus, DBeaver, and even the command line. One challenge is dealing with large result sets. How does your client handle that? Also curious if you plan to support multiple databases or keep it strictly MySQL-focused; honing in on one can sometimes yield better results.
What features does your client offer that TablePlus doesn’t have?
The key difference here is that your client is open-source, while TablePlus is a commercial product. So, the flexibility and community contributions could set your project apart.
Not at the moment, but it's a possibility for the future since the frontend technologies are web-based.