Re: pgAdmin 4 v2.0 Release Candidate 2

On Wed, Sep 27, 2017 at 7:58 AM, Johann Spies <jspies(at)sun(dot)ac(dot)za> wrote:

> pts rule name description
> ---- ---------------------- ------------------------------
> --------------------
> -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP
> 0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
> domain
> 2.5 BAYES_50 BODY: Bayes spam probability is 40 to 60%
> [score: 0.5000]
> X-Pg-Spam-Score: -4.2 (----)
>
> On Tue, Sep 26, 2017 at 09:13:42PM +0100, Dave Page wrote:
>
> > pgAdmin III is a different application. It’s been discussed a number
> > of times that pgAdmin 4 was never intended to be a carbon copy.
>
> This remark seems to me a bit mischievous. You seem to intentionally
> distort Melvyn's complains - much like politicians do.
>
> He has got valid arguments. Try and listen to him please.
>

I never said I wasn't listening - I'm already planning to try to sneak the
feature he asked for into 2.0.

However, what I said stands; we *intentionally* left many features out of
pgAdmin 4, as well as unintentionally missing a few (which we're working to
add back in as people ask for them). pgAdmin 4 was never intended to be a
carbon copy of pgAdmin III, specifically because part of the task was to
get rid of unused features that cost time and effort to maintain. That's
perfectly normal in the software world - and also happened in the
transitions to pgAdmin II and pgAdmin III from the earlier versions.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company