Postgres Pro
Downloads
Home   >   mailing lists

Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4) - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4)
Date
Msg-id CA+OCxoxKUd6eFGeCsb9Q0v6xfjEPSvBPMwxwp882KHyG35cx1g@mail.gmail.com
Whole thread Raw
In response to PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4)  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
Responses Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4)  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
List pgadmin-hackers
Tree view 
On Wed, Jun 22, 2016 at 7:14 AM, Murtuza Zabuawala
<murtuza.zabuawala@enterprisedb.com> wrote:
> Hi,
>
> PFA patch to fix the issue in server port check constraint validation which
> was not allowing user to save port 65535. (RM#1388)
>
> We have changed in server table definition hence user has to run "setup.py"
> again to fix the issue.

Hmm, I think we need to extend pgAdmin4.py to do that upgrade
automatically, in the same way that it will automatically run setup if
the database doesn't exist. Can we add a version check there, and
upgrade if needed?

--
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: Murtuza Zabuawala
Date:
Subject: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4)
Next
From: Murtuza Zabuawala
Date:
Subject: PATCH: Do not allow to drop current maintenance DB