Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4)
| От | Murtuza Zabuawala |
|---|---|
| Тема | Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4) |
| Дата | |
| Msg-id | CAKKotZR+ZbpM_cmcKpn3-7fkoj=aq_RxKYfiJFxgL4GY4t6pqw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PATCH: To fix the issue of IntegrityError in server port defination (pgAdmin4) (Dave Page <dpage@pgadmin.org>) |
| Ответы |
Re: PATCH: To fix the issue of IntegrityError in
server port defination (pgAdmin4)
|
| Список | pgadmin-hackers |
Sure.
--
Regards,
On Wed, Jun 22, 2016 at 1:35 PM, Dave Page <dpage@pgadmin.org> wrote:
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 по дате отправления: