11–16 of 16 posts
I am currently working on a mobile-first Postgres client. I am convinced that you are right about (desktop) database clients not being as powerful as they should be. Postgres in particular makes a lot of schema information available, but very few database clients make full use of it.
For collab: check out either Metabase or Apache Superset. I've used Metabase in the past for sharing SQL queries as snippets or as graphs, and I miss it sometimes. I am currently working on a mobile-first Postgres client. I am convinced that you are right about (desktop) database clients not being as powerful as they should be. Postgres in particular makes a lot of schema information available, but very few database…
This category of tools definitely scratches a big part of the itch here. But you still end up needing a db client for a long tail of other tasks. So now your db knowledge is spread across 3+ tools: shared queries/charts in Metabase, personal queries in Postico, schema defs and SQL files in your code repo, Notion, etc.
I think you've got an opportunity to consolidate all that into 1 tool in the same way Postman did for APIs
> Postgres in particular makes a lot of schema information available, but very few database clients make full use of it. Completely agree. Also just the industry consolidation around the pg ecosystem in general will lend itself to better tooling potential (e.g. Supabase's LSP project).
> I am currently working on a mobile-first Postgres client. Great that you're working on something new here! If I may ask - why mobile-first? That's not something I've particularly needed tbh (sample size of 1 of course)
For collab: check out either Metabase or Apache Superset. I've used Metabase in the past for sharing SQL queries as snippets or as graphs, and I miss it sometimes. I am currently working on a mobile-first Postgres client. I am convinced that you are right about (desktop) database clients not being as powerful as they should be. Postgres in particular makes a lot of schema information available, but very few database…
Oh yes I've been trialing Metabase but didnt know about Superset, thank you! This category of tools definitely scratches a big part of the itch here. But you still end up needing a db client for a long tail of other tasks. So now your db knowledge is spread across 3+ tools: shared queries/charts in Metabase, personal queries in Postico, schema defs and SQL files in your code repo, Notion, etc. I think you've got an o…
This is a very fair question. The short answer is that there are times when I wished I could look stuff up on our databases on my phone, but the tooling available for this is kinda meh
The longer answer is that there are now way more smartphones than PCs in the world, but we still don't have good ways to do software engineering on smartphones. I want to explore this space more, using SQL as a wedge to crack open the problem space.
It has sophisticated filters and you can share reports with your team (as opposed to exporting CSVs).
Have you looked at DataSpell? I haven't used it myself but it looks like it fits at least some of what you need. https://www.jetbrains.com/dataspell/
Happy to be schooled though.