From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
Cc: | George Gelashvili <ggelashvili(at)pivotal(dot)io>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: To fix the issue in Database node (pgAdmin4) |
Date: | 2017-01-25 13:09:17 |
Message-ID: | CA+OCxozSsKyenRFO+XCnNc6QPPPzvoZYVu22q4E=L4Q+7zf1Cg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Wed, Jan 25, 2017 at 12:21 PM, Murtuza Zabuawala
<murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> Last patch had Python-3 fix for test suite, but now it is already committed.
> PFA updated patch.
It still doesn't work completely for me. I tried changing the value of
bytea_output in a database that *does* allow connections, and I get a
503 response from the server, with a message of:
{"info":"CONNECTION_LOST","errormsg":"Connection to the server has
been lost!","data":{"database":null,"conn_id":null,"sid":1},"result":null,"success":0}
The payload sent via PUT to
http://127.0.0.1:5050/browser/database/obj/1/1/12403 was:
{"id":12403,"variables":{"changed":[{"role":"pgweb","name":"bytea_output","value":"hex","database":"postgres"}]}}
It works fine without the patch applied.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-01-25 13:21:42 | pgAdmin 4 commit: Enable/disable NULLs and ASC/DESC options for index c |
Previous Message | Murtuza Zabuawala | 2017-01-25 12:21:52 | Re: PATCH: To fix the issue in Database node (pgAdmin4) |