Using DBeaver

DBeaver provides access to production postgres databases via the command line.

Prerequisites

Before using DBeaver, you’ll need to run the following commands in the command line:

brew update && brew upgrade postgres-connect
brew install --cask dbeaver-community

This will install postgres-connect and DBeaver.

Caveats / Changes to postgres-connect

In this release we added the --show=dbeaver command. We still default to pgadmin3 for those of you who want to use pgadmin… for now.

For DBeaver, we do not pull the list of servers that we used to pull for implementation and support. That means you need to know which database in on which server, but I’m sure you all will get the hang of it.

Actually running the dang thing

In the command line enter:

postgres-connect connect --role implementation --name pg-banno --env prod -d banno_all --show=plain

This will get you access to banno_all on postgres1. You can replace postgres1 and banno_all with whatever database and server you’d like to connect to.

First run

On your first run it MAY prompt you to create a sample database, keep hitting no until it decides that you really don’t want to create a sample database. After that, it will bring you to a screen with a “download” button on it. Hit download, this installs the “driver” for postgres. After that, you can use DBeaver very similarly to how you used pgadmin.

Quitting the dang thing

When you’re done using DBeaver hit ctrl-c in the terminal to close it.