Re: [pgAdmin4][Patch][RM_1918] : Implement the DB restriction fieldfrom pgAdmin III - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin4][Patch][RM_1918] : Implement the DB restriction fieldfrom pgAdmin III
Date
Msg-id CA+OCxoyKPthz7hYLLG29SZqM6NbaprvGGsRu3M2LZt0pi_GXpw@mail.gmail.com
Whole thread Raw
In response to [pgAdmin4][Patch][RM_1918] : Implement the DB restriction field frompgAdmin III  (Atul Sharma <atul.sharma@enterprisedb.com>)
List pgadmin-hackers
Thanks, patch applied!

A couple of tips for the future:

- Please ensure screenshots are of a comparable size to the ones around them or that they replace. We sometimes see extra-large screenshots where they've been taken on hi-res screens, often in an VM.

- Please be more generous with spaces, e.g.

func_name(a,b) should be func_name(a, b)

or

if (dave.isHungry()){
    dave.feed('Sammich')
}

should be

if (dave.isHungry()) {
    dave.feed('Sammich')
}

It makes it all a little more readable :-)

Thanks again.

On Fri, Jul 21, 2017 at 11:01 AM, Atul Sharma <atul.sharma@enterprisedb.com> wrote:
Hi,

Please find attached patch for RM#1918 : Implement the DB restriction field from pgAdmin III

Thanks,
Atul



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

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

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Add a field to the Server Dialogue allowing usersto
Next
From: pgAdmin 4 Jenkins
Date:
Subject: Build failed in Jenkins: pgadmin4-master-python34 #249