For the import connections feature? I can add that in, when I added the feature most people were coming from dbeaver and tableplus so just stuck to that.
>it's a breeze to work with if you just get through them not updating the crate officially on crates.io but the community has found the solutions for it, you just have to dig deep for it
Basically finding which distribution to go with, there is gpui-ce, gpui-pre because the zed team last updated their crate more than a year ago so people publish it by their own. I have found gpui kit to be the best since it adds a retained mode too I want to ultimately play around with
just had a quick google too because gpui is on my “to check out some time” list and the situation honestly does not inspire confidence
it seems like everyone and their dog has their own vibe coded gpui flavor and the choice is between making your own vibe coded gpui flavor instead of your desired project vs building your project on quicksand
i feel like the problem is that (putting together a website, making a bunch of commits, getting people interested) was at some point a sign of a base level of commitment
now that the cost of that is zero it’s difficult to say whether a “community edition” actually has any community which will still be there next quarter
oh well sorry for the rant good on you for making it work clearly it is possible
Oh this is good news — I have been looking for a fuss-free cross-platform alternative to MySQL Workbench to recommend for a data product for some time.
(Workbench is a pain but it was capable, off-the-shelf and was possible to document it once, more or less, for multiple platforms; I did not actually hate using it. But alas it is old now)
DBX is great but it uses tauri, it is better than using jvm and electron but still doesn't provide the performance gains GPUI does or any other native framework would do.
Yes, and UX. Doing the fundamental things but doing them really well. I like zed's approach where they were slow to add features and weren't/aren't at feature parity with VSCode but the point was to get out of the way for most of your workflows. I'm basically going with the same idea in mind.
Performance is a hard sell when most of the time is going to be spend waiting on the DB for queries, isn't it? (compared to dbx - anything in Java is going to naturally be larger for this).
Or are you thinking of performance in terms of UX when browsing the result-sets?
But, congrats on the project. It looks great. I can't wait to try it.
Yes, the slow queries stay but there are some differences:
Same result set where other clients can crash, this scrolls smoothly so you can naturally load a bigger result set in the app than other clients would allow you to,
It paints the UI considerably faster than DBeaver on my benchmarks, thats after the query has run.
Memory footprint for the same result is considerably lower.
Basically, your db client can slow you down even after you have waited for queries so this will fix that.
Voluntary sponsors is the plan for now, I've been fairly consistent with the development for the last few months so I'm fairly confident this won't be abandoned. However, I would love to create a community around it and get some consistent contributors.
I hear you, although I must say I'm very interested in trying this out. It doesn't look like slop, and honestly all db clients I've used have somehow felt inredibly sloppy.
For me, and for customers I want to document things for, it has come down to MySQL Workbench on the free/open source side of things.
I want to support multiple platforms without having to fundamentally document multiple strategies.
Most DB tools feel like they will go the way of PostgreSQL or Insomnia — get slowly burdened with cloud facilities and then a bait-and-switch means you need a login somewhere.
I would much rather be able to talk about clients that do fewer tasks but do them well, but DB clients do seem to be prime enshittification territory for some reason.
Thanks for working on this! All db clients I've used have felt very bloated and I relate to your experience of crashes. I will definitely try this out!
One thing missing in all the GUI clients I know for Postgres's is being able to work with composite types and filtering them like `(IMT, 1)`. Similar as edit things like this, arrays, json, etc
I haven't use datagrip much so can't tell exactly but the editor is schema aware and does provide auto completions. You can take it for a spin and just open issue for things you find lacking if possible and I'd work on adding those.
Looks nice, though it does not open .sqlite files on Windows, when they are somewhere in the WSL filesystem. But neither does DBeaver. dbx opens them just fine though.
> I wanted something which is performant, modern and consumes little ram. The existing DB clients are either filled with bloat (Electron and JVM) or paid. This is an alternative to them.
There are many, many existing DB clients. Some of them already written in GPUI and free/open source:
I've never used navicat but for dbeaver, its not at parity because dbeaver offers a lot of features which it doesn't yet.
The data destruction thing was something I was really careful with, any destructive query opens a confirmation first, any edit opens a popup showing the query that will run. I've designed it to be really safe.
For perf, even if row listing speed doesn't matter I assume scrolling and loading a large dataset would improve your workflow, plus quick tab switches and low memory usage for all, no?
written-beyond | 22 hours ago
[OP] shayan_abbas | 21 hours ago
edstarch | 21 hours ago
what does this mean?
the ui does look very nice
[OP] shayan_abbas | 21 hours ago
edstarch | 21 hours ago
just had a quick google too because gpui is on my “to check out some time” list and the situation honestly does not inspire confidence
it seems like everyone and their dog has their own vibe coded gpui flavor and the choice is between making your own vibe coded gpui flavor instead of your desired project vs building your project on quicksand
i feel like the problem is that (putting together a website, making a bunch of commits, getting people interested) was at some point a sign of a base level of commitment
now that the cost of that is zero it’s difficult to say whether a “community edition” actually has any community which will still be there next quarter
oh well sorry for the rant good on you for making it work clearly it is possible
dofm | 21 hours ago
(Workbench is a pain but it was capable, off-the-shelf and was possible to document it once, more or less, for multiple platforms; I did not actually hate using it. But alas it is old now)
I will surely test this out; good luck with it.
[OP] shayan_abbas | 21 hours ago
exaroth | 21 hours ago
[OP] shayan_abbas | 21 hours ago
dubcanada | 21 hours ago
[OP] shayan_abbas | 21 hours ago
mbreese | 21 hours ago
Or are you thinking of performance in terms of UX when browsing the result-sets?
But, congrats on the project. It looks great. I can't wait to try it.
[OP] shayan_abbas | 21 hours ago
Same result set where other clients can crash, this scrolls smoothly so you can naturally load a bigger result set in the app than other clients would allow you to, It paints the UI considerably faster than DBeaver on my benchmarks, thats after the query has run. Memory footprint for the same result is considerably lower.
Basically, your db client can slow you down even after you have waited for queries so this will fix that.
mikenikles | 21 hours ago
How do you sustain continuous development of the project beyond the next two weekends?
[OP] shayan_abbas | 21 hours ago
edem | 20 hours ago
logdahl | 20 hours ago
dofm | 19 hours ago
For me, and for customers I want to document things for, it has come down to MySQL Workbench on the free/open source side of things.
I want to support multiple platforms without having to fundamentally document multiple strategies.
Most DB tools feel like they will go the way of PostgreSQL or Insomnia — get slowly burdened with cloud facilities and then a bait-and-switch means you need a login somewhere.
I would much rather be able to talk about clients that do fewer tasks but do them well, but DB clients do seem to be prime enshittification territory for some reason.
dofm | 15 hours ago
Brain concept leakage there. I meant all those apps that start off with a simple purpose and end up with an enterprise cloud plan.
fhn | 18 hours ago
mrgoldenbrown | 20 hours ago
[OP] shayan_abbas | 20 hours ago
logdahl | 20 hours ago
mamcx | 20 hours ago
MrDrMcCoy | 19 hours ago
[OP] shayan_abbas | 18 hours ago
mamcx | 13 hours ago
[OP] shayan_abbas | 24 minutes ago
written-beyond | 18 hours ago
But I absolutely hate opening DataGrip it feels like you're trying to start a crank car from the 40's.
[OP] shayan_abbas | 2 hours ago
brumbelow | 18 hours ago
godockly | 18 hours ago
[OP] shayan_abbas | 10 hours ago
upmostly | 17 hours ago
[1] https://dbpro.app
[OP] shayan_abbas | 11 hours ago
upmostly | 8 hours ago
What features are paywalled?
olive-n | 17 hours ago
[OP] shayan_abbas | 11 hours ago
gmmachine | 17 hours ago
I'd like an AI agent plugin to help with my SQL queries?
[OP] shayan_abbas | 10 hours ago
Why proof of concept though? There are people daily driving it
waterTanuki | 15 hours ago
There are many, many existing DB clients. Some of them already written in GPUI and free/open source:
https://github.com/0xErwin1/dbflux
NetOpWibby | 7 hours ago
Would you be interested in adding support for Disc?
https://disc.sh + https://disc.md
elxr | 5 hours ago
Natfan | an hour ago
d0100 | an hour ago
How does this compare with Navicat or DBeaver feature-wise?
[OP] shayan_abbas | 37 minutes ago
The data destruction thing was something I was really careful with, any destructive query opens a confirmation first, any edit opens a popup showing the query that will run. I've designed it to be really safe.
For perf, even if row listing speed doesn't matter I assume scrolling and loading a large dataset would improve your workflow, plus quick tab switches and low memory usage for all, no?