11–20 of 26 posts
1. The tools are always web based and have a bloated and bad experience as opposed to a complete native app. 2. Charts, easy ability to find the database if there are so many
See autocad for web for example, is kinda the same. Or Photopea, photoshop's clone.
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)?
> 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)?
Is that concept built in somewhere?
how did you manage to put - no bloat - built-in AI co-pilot with ollama (local) or openai/anthropic into one list?
[0]: https://github.com/clidey/whodb/blob/main/core/src/llm/llm_c...
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
"Conversate With Your Data: No more wasting time crafting complex SQL queries - ask away!" 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
how did you manage to put - no bloat - built-in AI co-pilot with ollama (local) or openai/anthropic into one list?
Cool product. > No more wasting time crafting complex SQL queries 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
People confuse the two, and rightfully dislike the former while dangerously resenting the latter.