I would feel uncomfortable saying the word 'beaver' at work.
Why? Is it a bad word in some language?
Dbeaver – Multi-platform database tool
41–50 of 209 posts
Re: Dbeaver – Multi-platform database tool
#42I prefer TablePlus personally, DBeaver just feels clunky in comparison.
Re: Dbeaver – Multi-platform database tool
#43I am missing bigger screenshots though, I tried opening them separate but they are quite small.
Re: Dbeaver – Multi-platform database tool
#44I prefer TablePlus personally, DBeaver just feels clunky in comparison.
Re: Dbeaver – Multi-platform database tool
#45Re: Dbeaver – Multi-platform database tool
#46Re: Dbeaver – Multi-platform database tool
#47I would feel uncomfortable saying the word 'beaver' at work.
- Bob unzip a Python package.
- Dennis suggested we hire a "penetration tester".
- Mrs. Fraulein was caught browsing "Jew Tube".
- Helen used an essential software product from a "Pentaho"company for more than three years. Mr. Flanders was so disturbed he bought that company and renamed it "Itachi Vantara".
- Raul was using "Zope" to build our Intranet, until our Purity squad learned it was an insult in Spanish.
- David boasted about installing "OpenSIS" at his university.
- Susan was reported for surreptitous use of "ClamAV".
I also recommend terminating Derek for using "Google". It's not in the blacklist, but it just sounds obscene.
Re: Dbeaver – Multi-platform database tool
#48Re: Dbeaver – Multi-platform database tool
#49Re: Dbeaver – Multi-platform database tool
#50I like to try out new tools likes this, but whilst on my mac, and I generally use Sequel Pro for my databases (I use mysql and mariadb drop-ins). I have my database locally in a docker container, where I forward 3306 to 3300. Entering host as 127.0.0.1 with correct credentials and port, it gives me this error: "Could not connect: Access denied for user 'root'@'172.18.0.1'". This does not happen with Sequel, but occur…
This sounds like a docker network problem more than an issue with dbeaver. Try binding MySQL to 0.0.0.0 (all interfaces) instead of 127.0.0.1 (loopback). That said, 127.0.0.1 should be fine provided you connect through the service name or the docker container IP), connecting via 127.0.0.1 doesn't make sense. Then again, it's docker on Mac, so I don't really know. Fwiw, also used sequel pro on Mac, moving to Linux dbe…