Hi, my name is Anguel and I am one of the developers of WhoDB (<a href="https://github.com/clidey/whodb">https://github.com/clidey/whodb</a>)<p>I am not a fan of the dbeaver, beekeeper, adminer, etc experience because they are bloated, ugly, and at best okay but not great.<p>Hence why I started working on WhoDB.<p>The approach:<p>- browser-based (chrome/firefox)<p>- no bloat<p>- jupyter notebook-like experience (Scratchpad)<p>- built-in AI co-pilot with ollama (local) or openai/anthropic<p>We just shipped query history and replay (time travel?) to the Scratchpad.<p>Would love for you to check it out and give some feedback aka roast us into oblivion:<p>docker run -p 8080:8080 clidey/whodb<p>Food for thought:<p>1. What's your biggest database pain point?<p>2. Any killer feature missing from current tools?
Cool product.<p>> No more wasting time crafting complex SQL queries<p>I always wondered about this sentiment; isn't the time spent crafting complex queries a good thing when trying to understand a problem domain? I.e. incrementally refining your mental model of the data model
When talking about Time Travel in regards to a database, that term usually means "seeing what the data looked like at a specific time". From my brief skim here, I don't see that.<p>Is that concept built in somewhere?
> query history and replay<p>For clarification- am I correct that what you are referring to as "time travel" is simply a history list of prior queries you've run? Can I today, run a query and see what the results would have been in the database last month (or yesterday, or 2 hours ago, etc)?
Unsolicited feedback (or I guess solicited reading the post again): Juypter Notebook experience got me to click because I thought this might be like a Deepnote alternative<p>But the only screenshot on the Github page was decidedly not that. It wasn't showing something very appealing visually, or immediately obvious in terms of necessity for a tool calling its competitors ugly and bloated<p>I don't use any of the ones you listed so maybe they're even uglier, but I would maybe tweak the pitch and make it clearer who this is for
1. The tools are always web based and have a bloated and bad experience as opposed to a complete native app.<p>2. Charts, easy ability to find the database if there are so many
Nice product! I'm also not a big fan of DBeaver, Beekeeper, or Adminer. However, I do use HeidiSQL, and it's been lightweight and robust for me over the last 20 years. One feature I really appreciate is the query history, which is categorized by date. Have you ever given it a try?
> I am not a fan of the dbeaver, beekeeper, adminer, etc experience because they are bloated, ugly, and at best okay but not great<p>What you call "bloated", I call "features". What you call "ugly", I call "functional".
"Conversate With Your Data: No more wasting time crafting complex SQL queries - ask away!"<p>Maybe it is just me but literally every single product that has tried to eliminate SQL somehow with a conversational interface has never seen mass success, if they did, we wouldn't be using SQL anymore