←back to thread

Show HN: Time Travel with Your SQL

43 points modelorona | 3 comments | 10 Apr 25 22:48 UTC | HN request time: 0.914s | source

Hi, my name is Anguel and I am one of the developers of WhoDB (https://github.com/clidey/whodb)

I am not a fan of the dbeaver, beekeeper, adminer, etc experience because they are bloated, ugly, and at best okay but not great.

Hence why I started working on WhoDB.

The approach:

- browser-based (chrome/firefox)

- no bloat

- jupyter notebook-like experience (Scratchpad)

- built-in AI co-pilot with ollama (local) or openai/anthropic

We just shipped query history and replay (time travel?) to the Scratchpad.

Would love for you to check it out and give some feedback aka roast us into oblivion:

docker run -p 8080:8080 clidey/whodb

Food for thought:

1. What's your biggest database pain point?

2. Any killer feature missing from current tools?

1. listenallyall ◴[11 Apr 25 16:46 UTC] No.43655860[source]▶
> query history and replay

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)?

replies(1): >>43656271 #
2. tarasyarema ◴[11 Apr 25 17:27 UTC] No.43656271[source]▶
I also understood that, but seems unreasonable to be able to achieve it without somehow storing the state via scd or some sort of audit + multi engine support
replies(1): >>43661092 #
3. listenallyall ◴[12 Apr 25 03:29 UTC] No.43661092[source]▶
Sure it's a complex, difficult feature. But that's what "time travel" typically means in terms of querying databases. It's the headline of this article, the fact that what they really mean is a simple query log, is kind of bait-and-switch.