- Postico OSX - https://itunes.apple.com/us/app/postico/id1031280567?ls=1&mt...
- JackDB (web based) - https://www.jackdb.com/
- SQL Pro for Postgres - http://www.hankinsoft.com/SQLProPostgres/
- PGAdmin - Slightly outdated but still feature rich and fully cross platform - http://www.pgadmin.org/
And of course there's always psql which is all CLI, but incredibly flexible.
- PG Commander (free): a lighter version of Postico - https://eggerapps.at/pgcommander/
- Sequel Pro (donationware): a nice native GUI browser for MySQL - http://www.sequelpro.com/
It's especially useful if you're already using it on your day/consulting job as it naturally blends into the environment.
I'm excited to see all the work that's going into tools to work with Postgres :)
I'm not sure why more db tools don't follow that paradigm.
It's pretty rare - mostly for ad-hoc interactive debugging, typically where there's some UI missing or not yet implemented - that you'd want to edit a single row's contents.
In fact, if I'm not wrong there was a startup that got launched on HN or PH or somewhere that just builds database connected spreadsheet-like webapps.
The thing is - in operations driven startups, the early days are built on top of spreadsheets. Which can get unmanageable within days. So then you start building your webapp. Something like dbeaver turns into a godsend because you then use the database as a spreadsheet, while you take your time building the webapp.
A spreadsheet is so much more common than a webapp with an opinionated UI - it was so surprising that when I handed over dbeaver to an operations guy, he actually had zero trouble using it to do his work. In fact the UI we are building now is on top of Handsontable (a JS spreadsheet component) rather than a form-like web component. Everyone is just so used to copy pasting rows, manipulating data,etc.
I would presume that most DB's are installed on UNIX based systems so most of the people who are developing tools for them are going to already be on such systems.
What I mostly miss is a good tool focused on writing SQL like Management Studio from MS SQL Server. Something that allows me to easily open complex large scripts in a full editor, execute parts or all of it easily and get results back. Not much gui, not many wizards, but a good experience. Most tools I find for pg are either full console or full guis with too much focus on wizards. It's like the people using it are uncomfortable with SQL for some reason.
But having followed pg for 15 years or so, I don't think they want or need to be the most popular database. They just want to be a damn good database server, and they are.
Note that I'm not from the US, I'm from Brazil. Here windows pretty much dominates the landscape.
But this is also important: while the US is currently quite apple-centric, most countries are not. And although the US concentrates a lot of tech companies, it's still only 4% of the world.
I'm not stating that these stats are the ultimate sources of truth. But those are good references. If you were to measure the reality in most countries, I doubt those numbers would swap places.
In Brazil I see lots of devs using Macs too. It's just not the majority of them.
So even corporate world is changing.
Maybe I am missing something, but I am not seeing a way to dig into a given database's structure without cumbersomely querying the pg_catalog. Noticeably absent are \dt and such vs running stuff like
SELECT n.nspname as "Schema",
c.relname as "Name",
CASE c.relkind WHEN 'r' THEN 'table' WHEN 'v' THEN 'view' WHEN 'i' THEN 'index' WHEN 'S' THEN 'sequence' WHEN 's' THEN 'special' WHEN 'f' THEN 'foreign table' END as "Type",
pg_catalog.pg_get_userbyid(c.relowner) as "Owner"
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r','')
AND n.nspname <> 'pg_catalog'
AND n.nspname <> 'information_schema'
AND n.nspname !~ '^pg_toast'
ORDER BY 1,2;
Database Info from the menu seems to be similar to \d and a few others, but it's for the whole database and not a specific schema.
Still, I will keep playing with this and see how it goes.