3 ms·

Nothing beats the freedom and universality of the command line or using APIs (with a small utility library) in a repl of the language of your choice.

garciasn 3y ago
I mean, you're not wrong: there is absolutely a big place for API/CLI support with DB tools, but in this specific instance, the OP specifically asked for a GUI, not CLI or APIs to roll their own. If you're a MacOS user and your DB of choice is supported, this is my choice: https://www.beekeeperstudio.io/ https://www.beekeeperstudio.io/ If you're a Postgres user, pgAdmin had previously been my go to: https://www.pgadmin.org/ https://www.pgadmin.org/
- seeknotfind 3y ago
  If OP asked which cliff he should jump off, will you point to one? GUIs are written on top of DB APIs - in many cases, the same ones you can use. You can do anything with these tools. Given a DB viewing program, you are always experiencing someone else using these APIs for you. There will always be some feature you need. For many types of applications, there are no other choices except the GUI, but DBs are programmer tools, and they work brilliantly without gold-plated rigmarole.
  - kadomony 3y ago
    Yeah, but I did ask for GUIs for a reason. Other commenter understood the assignment.
    - seeknotfind 3y ago
      What reason?
  - garciasn 3y ago
    Dude. Are you for real right now? I work with data all day and have for 20+ years. I *STRONGLY PREFER* to develop my code in a UI and then later deploy it to the production infrastructure via CLI/API. I just cannot possibly fathom how you could seriously tell someone working with data that they should interact with their systems in a CLI/API way all the time; it just doesn't make any sense whatsoever, unless you are dealing with queries and their results that are not at all complex. There is a place and a time for both paradigms and to suggest that we should direct someone away from their preferred use case is really over the top.

garciasn 3y ago

I mean, you're not wrong: there is absolutely a big place for API/CLI support with DB tools, but in this specific instance, the OP specifically asked for a GUI, not CLI or APIs to roll their own. If you're a MacOS user and your DB of choice is supported, this is my choice: https://www.beekeeperstudio.io/ https://www.beekeeperstudio.io/ If you're a Postgres user, pgAdmin had previously been my go to: https://www.pgadmin.org/ https://www.pgadmin.org/

seeknotfind 3y ago
If OP asked which cliff he should jump off, will you point to one? GUIs are written on top of DB APIs - in many cases, the same ones you can use. You can do anything with these tools. Given a DB viewing program, you are always experiencing someone else using these APIs for you. There will always be some feature you need. For many types of applications, there are no other choices except the GUI, but DBs are programmer tools, and they work brilliantly without gold-plated rigmarole.
- kadomony 3y ago
  Yeah, but I did ask for GUIs for a reason. Other commenter understood the assignment.
  - seeknotfind 3y ago
    What reason?
- garciasn 3y ago
  Dude. Are you for real right now? I work with data all day and have for 20+ years. I *STRONGLY PREFER* to develop my code in a UI and then later deploy it to the production infrastructure via CLI/API. I just cannot possibly fathom how you could seriously tell someone working with data that they should interact with their systems in a CLI/API way all the time; it just doesn't make any sense whatsoever, unless you are dealing with queries and their results that are not at all complex. There is a place and a time for both paradigms and to suggest that we should direct someone away from their preferred use case is really over the top.