On 2017-05-20 14:23, Raymond O'Donnell wrote:
On 20/05/17 11:17, rich...@xentu.com wrote:
On 2017-05-19 14:45, rich...@xentu.com wrote:
On 2017-05-19 14:20, Adam Brusselback wrote:
I seriously may go back to PostgreSQL 9.3 so that I can use pgAdmin
III until I can wean myself off the tool.
Y
On 20/05/17 11:17, rich...@xentu.com wrote:
On 2017-05-19 14:45, rich...@xentu.com wrote:
On 2017-05-19 14:20, Adam Brusselback wrote:
I seriously may go back to PostgreSQL 9.3 so that I can use pgAdmin
III until I can wean myself off the tool.
You don't have to revert your database version t
On 2017-05-19 14:45, rich...@xentu.com wrote:
On 2017-05-19 14:20, Adam Brusselback wrote:
I seriously may go back to PostgreSQL 9.3 so that I can use pgAdmin
III until I can wean myself off the tool.
You don't have to revert your database version to use pgadmin III,
the newest release works f
Am 18.05.2017 um 22:43 schrieb Dave Page:
> Not to me, because the number of people I've had complimenting pgAdmin 4
> is probably 20x the number who have said they don't like it. Which is a
> good sign - normally people who don't like something are far more likely
> to say something.
People who
On 2017-05-19 16:07, Michael Shapiro wrote:
> FWIW -- the final release of PgAdmin 3 fixed an ssl issue which, at
> least for me, fixed the disconnects from the server.
Not me. I still can't use it for more than a few minutes at a time, or
with a query that returns more than a few dozen rows, if S
