Live data from Hacker News

Dbeaver – Multi-platform database tool

dbeaver.io

41–50 of 209 posts

Re: Dbeaver – Multi-platform database tool

#47
post #14

I would feel uncomfortable saying the word 'beaver' at work.

Causes of termination at bart3r's company last month:

- 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

#49
post #36

Earlier quoted context omitted.

DataGrip:DBeaver::IntelliJ:Eclipse

Not sure what you are trying to say.

DataGrip is essentially a stripped down version of IntelliJ packaged with their database plugin. Dbeaver is similar but using the Eclipse framework instead.

Re: Dbeaver – Multi-platform database tool

#50
post #39
post #32

I 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…

I know I can solve that by allowing "everytuldhing" to connect, but that is not my point. Hence my ""I'm sure that it could be solved in my configs by allowing that particular IP"" comment. That it's `Docker on mac` is kinda irrelevant, as it's still just a virtual machine with a somewhat static IP. My point is, that when it comes to transparency on that level, this piece of software does not acknowledge that, but Sequel Pro does. I'm not a particular fan of Sequel Pro, but it just works in these types of case. I'm still expecting, that software like this, would be able to handle this type of "proxy mechanism", so from outside the docker container, I could still connect through 127.0.0.1 to it, thus making the default config adequate. Not sure if this is even makes sense, but I feel, that when connecting through a binding docker port, it should still use the origin IP ie. 127.0.0.1
Post reply on HN