|
|
|
|
|
by wink
2706 days ago
|
|
Just installed it for the first time in a few years. - Again I wonder why it doesn't show the tables first, I have to go through Schemas -> Public. - 480 MB of RES RAM, I'm connected to one smallish Postgres DB. - I can't even find "just show me the contents of the table, like 'SELECT * FROM'. I know, maybe it's tailored for Enterprise Database Architects, but this is my smoke test for a DB GUIs: "How long and how many clicks does it take so that it provides more value than: 'psql; \dt+; SELECT * FROM X;'" |
|
Mouse over the buttons for an excessive amount of time and the tooltips will tell ya what they do.
Double click a table and go to "data" tab to see contents.
Schemas ->public is just a side effect of supporting a lot of different databases. Many support schemas
Ram is because default java heap size, you could probably change launch params to get it much lower though.
On all counts other DB tools I've used are just as obtuse and burn tons of resources. Most are written in Java or another high-level language because it's nigh impossible to get DB drivers for a ton of different databases working together in C. DBeaver is basically leveraging JDBC for what it was designed for