Re: PG Admin 4

From: Miles Elam <miles(dot)elam(at)productops(dot)com>
To: susan(dot)hurst(at)brookhurstdata(dot)com
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PG Admin 4
Date: 2020-07-10 20:35:52
Message-ID: CAALojA_vmh_f2YisSE18p2+EeLyEo+Ff+4dSGNec=AonWSX6Sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I did the same for at least a year, but I must admit that v4 has improved
greatly since its initial release. Also it turns out is handy for running
in a docker-compose environment so no matter who is starting up on your
team, they always have a database and a database admin tool at the ready
along with the app.

On Fri, Jul 10, 2020 at 1:31 PM Susan Hurst <susan(dot)hurst(at)brookhurstdata(dot)com>
wrote:

> I gave up on PGAdmin4 and went back to PGAdmin3, although 3 is deprecated
> now. The History tab will show you what you want after executing a SQL
> statement.
>
> I don't use Windows any more than I have to but when I did try PGAdmin4 on
> windows, the feedback was sometimes there and sometimes not. Linux works
> better.
>
> That said, I agree that executing a script from a command line is the best
> approach for implementing DDL statements. You can capture the script and
> the output for further confirmation of success or failure.
>
> Sue
>
>
>
>
>
> ---
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Susan E Hurst
> Principal Consultant
> Brookhurst Data LLC
> Email: susan(dot)hurst(at)brookhurstdata(dot)com
> Mobile: 314-486-3261
>
> On 2020-07-10 15:20, Tim Clarke wrote:
>
> Why would you shun the ease of command line batch control?
> Tim Clarke MBCS
> IT Director
> Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420
>
> On 10/07/2020 17:36, rwest wrote:
>
> Oh sorry, should have specified that.
>
> We're running on a Windows platform.
>
> We're trying to avoid running anything command-line when doing DDL releases
> and leverage whatever PG Admin 4 can provide us. I'm just wondering why we
> don't see the results of each CREATE or ALTER statement as the script runs
> in the tool. That seems very strange to me. Is there some sort of setting
> or parameter that can force the tool to do this for us?
>
>
>
>
>
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
>
>
> Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 |
> Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1
> 647 503 2848
> Web: https://www.manifest.co.uk/
>
>
>
> Minerva Analytics Ltd - A Solactive Company
> 9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United
> Kingdom
>
>
> ------------------------------
>
>
>
> Copyright: This e-mail may contain confidential or legally privileged
> information. If you are not the named addressee you must not use or
> disclose such information, instead please report it to admin(at)minerva(dot)info
> Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd:
> Registered in England Number 11260966 & The Manifest Voting Agency Ltd:
> Registered in England Number 2920820 Registered Office at above address.
> Please Click Here https://www.manifest.co.uk/legal/ for further
> information.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-07-10 23:02:09 Re: Postgresql-12 taking more time to execute the query
Previous Message Susan Hurst 2020-07-10 20:30:45 Re: PG Admin 4