When I first open the dbeaver program, the tree is completely closed, so it takes 5 clicks on the caret icons to expand to the actual tables finally, and then I have to double click on the table that I then want to open.This takes up far too much mental burden than necessary especially when I'm in a flow and open up dbeaver to inspect the data in a table, and I have to slow down just to navigate the tree to the tables.
In this application, there are no extra clicks! The program opens to this screen by default where all the tables are listed on the left side, and it only takes one click to open any table. This has literally reduced the number of clicks just to open a table from dbeaver's 7 to just 1!
I would just Postico all the time as it's far faster and simpler to use, but there are certain advanced features in dbeaver that I need to use sometimes as well so I'd rather make dbeaver work for me all the time.
macOS: Use Homebrew to run brew install --cask dbeaver-community, or use MacPorts to run sudo port install dbeaver-community. A macOS installer is also available from the Download page on the DBeaver website.
I needed to build a large Java project.
After several builds, I encountered an OutOfMemoryError.
After analyzing the Dump file, we found a huge instance of org.jkiss.dbeaver.model.navigator.DBNModel that was over 1GByte.
This problem occurs with dbeaver version 4.2.2 and above.
My guess,
DBNEvent is accumulated in eventCache in org.jkiss.dbeaver.model.navigator.DBNModel$EventProcessingJob and it is OOME.
DBNModel.java has been refactored in 4.2.2 to add the internal class EventProcessingJob.
It seems that if you build a Java project after 4.2.2, the eventCache will continue to accumulate DBNEvents.
Commit ID: dbe4097035c407ab276e621773eed924c814f291
What can I provide to help resolve this issue?
Today I've a Problem with the autoincrement-BUG.
Google it has shown me, that DBeaver still is on 2.3, but in my eclipse-Update-Page-Settings I have a Link like:
dbeaver.jkiss.org/update/2.0/
I try toadExtension and dbeaver.
What i realy love on dbeaver... the chance to use ssh-tunnel for mysql-connection. This is a must-have for me, cause i don't open mysql-ports on a production-system... and i don't wanna manage ssh-tunnnel-connection outside of my eclipse (that all need time - and time is money ;)