5 ms·

Ask HN: What do you prefer web-based SQL client or desktop SQL client?

2 points by vioberoi 6y ago

I am trying to build a SQL client for Postgres and was curious to know what does everyone prefer?

the_arun 6y ago
Web-based makes it simple. But we need to run serverside code which connects to DB. But auth & auth can be externalized. If Desktop client, it has to support mac, windows & linux. And use auth & auth of DB. Another thing is, if it has to support multiple types of DB, eg MySQL, Postgres etc., it will get complex.
- vioberoi 6y ago
  Thanks! Any ideas on handling auth details on server side?
  - the_arun 6y ago
    Server side - we may need auth (google/github), roles and permissions - Roles - this could be as defined by DBAs. Admin, Developer, Analyst - is what I could think of at a high level. Permissions - We could define this at a table/view level. For eg. if you are developer, you could modify read/write these tables. If you are analyst - you could only read these tables. etc.,
  - the_arun 6y ago
    By the way thanks for asking. I guess this is turning out to be a cool project for High Schooler/Intern or anyone a pet project. Great job on the idea!
emteycz 6y ago
Web. I don't want to run Electron app, and I don't think you can maintain a multiplatform native-feeling app as a single developer; not having the client on all platforms is a dealbreaker to me.
- vioberoi 6y ago
  Sure! Thanks. Just curious to know why do you not want electron app.
  - emteycz 6y ago
    I have a browser open already. Some of the machines I use are resource constrained, I don't see a reason to have two browsers. I also like the option of remote access - I install the client (I am using Pgadmin 4) on my personal server or workstation and can access the DB easily from a familiar interface that remembers my settings. In combination with Postgraphile that gives me a portable and simple development environment for my personal app needs.
blakeburch 6y ago
Desktop. I've found that a lot of web-based SQL clients pose more limitations to how much data you can bring in, causing frustration. Additionally, it seems that the solution to running multiple queries on the web is to open more tabs of the application in your browser... which isn't ideal. Most of my work involves automating SQL through Python scripts so running queries on desktop solves the above problems and limits the amount of switching back and forth.
- vioberoi 6y ago
  Interesting! Any limitations you face for desktop-based clients?
  - blakeburch 6y ago
    Not that I can remember coming across. Most of the desktop clients are pretty smart and prevent large data loads from causing hangups. Back in the day, Wagon (https://www.wagonhq.com/ https://www.wagonhq.com/) was my favorite, but the team was bought by Box. PopSQL (https://popsql.com/ https://popsql.com/) has at least partially filled that void over the last 2 years. Happy to answer any specific questions you might have as you're building. Email is in my profile.

2 points by vioberoi 6y ago

I am trying to build a SQL client for Postgres and was curious to know what does everyone prefer?

Web-based makes it simple. But we need to run serverside code which connects to DB. But auth & auth can be externalized. If Desktop client, it has to support mac, windows & linux. And use auth & auth of DB. Another thing is, if it has to support multiple types of DB, eg MySQL, Postgres etc., it will get complex.

vioberoi 6y ago
Thanks! Any ideas on handling auth details on server side?
- the_arun 6y ago
  Server side - we may need auth (google/github), roles and permissions - Roles - this could be as defined by DBAs. Admin, Developer, Analyst - is what I could think of at a high level. Permissions - We could define this at a table/view level. For eg. if you are developer, you could modify read/write these tables. If you are analyst - you could only read these tables. etc.,
- the_arun 6y ago
  By the way thanks for asking. I guess this is turning out to be a cool project for High Schooler/Intern or anyone a pet project. Great job on the idea!

emteycz 6y ago

Web. I don't want to run Electron app, and I don't think you can maintain a multiplatform native-feeling app as a single developer; not having the client on all platforms is a dealbreaker to me.

vioberoi 6y ago
Sure! Thanks. Just curious to know why do you not want electron app.
- emteycz 6y ago
  I have a browser open already. Some of the machines I use are resource constrained, I don't see a reason to have two browsers. I also like the option of remote access - I install the client (I am using Pgadmin 4) on my personal server or workstation and can access the DB easily from a familiar interface that remembers my settings. In combination with Postgraphile that gives me a portable and simple development environment for my personal app needs.

blakeburch 6y ago

Desktop. I've found that a lot of web-based SQL clients pose more limitations to how much data you can bring in, causing frustration. Additionally, it seems that the solution to running multiple queries on the web is to open more tabs of the application in your browser... which isn't ideal. Most of my work involves automating SQL through Python scripts so running queries on desktop solves the above problems and limits the amount of switching back and forth.

vioberoi 6y ago
Interesting! Any limitations you face for desktop-based clients?
- blakeburch 6y ago
  Not that I can remember coming across. Most of the desktop clients are pretty smart and prevent large data loads from causing hangups. Back in the day, Wagon (https://www.wagonhq.com/ https://www.wagonhq.com/) was my favorite, but the team was bought by Box. PopSQL (https://popsql.com/ https://popsql.com/) has at least partially filled that void over the last 2 years. Happy to answer any specific questions you might have as you're building. Email is in my profile.