top | item 39665952

(no title)

samuelec | 2 years ago

I have been using it for 3 years with Postgresql and it still buggy. When the db is throwing out an error dbeaver just say that there was an error on line xx followed by java exception stactrace forcing me to login into the db via command line and figure out what is wrong myself. If you want to write and debug a stored procedure then good luck! The ui had many issues and only recently seems to be just usable. At least with Postgresql, I can't really recommend for anything too complex.

discuss

order

ajsnigrutin|2 years ago

For me it's buggy when it has to reconnect to something... eg. i work on something, close the laptop (suspend to mem), and the next day open it up, wait for an hour or two doing other stuff (so there's enough time to notice that the tcp session is down), and dbeaver shows a progress bar and gets stuck there, until i restart it, and click a zillion times to get to the proper psql table.

Also, the annoying 'new version,...' popups are annoying.

Otherwise, a great gui.

johnchristopher|2 years ago

> Also, the annoying 'new version,...' popups are annoying.

And the weird wording when you finish restoring a database with the button "next" highlighted, asking for one more ride.

dicknuckle|2 years ago

Agreed, I've had mostly the same experience. There was about a month where I wasn't able to run a particular query on Oracle SQL but that's fixed now.