That's a nice idea. I have been using DataGrip in the past, it is heavy. Then started to take a look at DBPro, it's much lighter in terms of UI, but again costs a lot of RAM due to electron usage and I have noticed a few issues there in terms of performance and capabilities.

Overall, from what I've tried, it's a nice project. It's a bit unfair to compare, but it lacks a things I'd need to switch from DataGrip. I hope this doesn't sound too harsh:

The optimiser itself is AI. Which I don't like, rewrites could be proved from the catalog (an unused unique LEFT JOIN, DISTINCT over a key, NOT IN to NOT EXISTS, OR to UNION). A model can suggest a rewrite, but it can't guarantee the result set is the same.

Also vim mode is editor only, for me its important to have the whole app keyboard native

The formatter is basic compared with DataGrip's code-style settings

DataGrip can step through PL/pgSQL and Oracle PL/SQL code. As far as I can tell TablePro has nothing similar, and in my work that's a blocker.

[dead]