Re: [pgadmin-hackers] Database child node: Cast node patch

2016-10-05 Thread Dave Page
On Wed, Oct 5, 2016 at 7:31 AM, Priyanka Shendge wrote: > > On 4 October 2016 at 19:36, Dave Page wrote: >> >> Hi >> >> On Tue, Oct 4, 2016 at 9:01 AM, Priyanka Shendge >> wrote: >> > I applied this patch on clean machine and executed testsuite only for >> > "cast" >> > node, i did not face any

[pgadmin-hackers] PATCH: To fix issue in synonym node (pgAdmin4)

2016-10-05 Thread Murtuza Zabuawala
Hi, PFA patch to fix the issue in synonym node, where it was not horning parent node while creating in different node, issue was that we were not sending node properly. RM#1611 Please review. -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Compan

[pgadmin-hackers] pgAdmin4 as web application on CentOS

2016-10-05 Thread Olav Peeters
Hi, I installed pgAdmin4 as follows on CentOS 7: yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-redhat96-9.6-3.noarch.rpm yum install pgadmin4 httpd mod_wsgi (on CentOS 7 this means httpd 2.4.6, mod_wsgi 3.4-12 and pgadmin4 1.0-1) This does not install pgA

[pgadmin-hackers] pgAdmin 4 commit: Fix SSL setup. Fixes #1817

2016-10-05 Thread Dave Page
Fix SSL setup. Fixes #1817 Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=bde3dd845b1128d598da0f633b73520aa628a110 Author: Murtuza Zabuawala Modified Files -- web/pgadmin/utils/driver/psycopg2/__init__.py | 3 ++- 1 file changed, 2

Re: [pgadmin-hackers] PATCH: To fix the issue where pgAdmin4 was not honouring ssl mode options (pgAdmin4)

2016-10-05 Thread Dave Page
Thanks, applied. On Wed, Oct 5, 2016 at 7:23 AM, Murtuza Zabuawala wrote: > Hi, > > PFA minor patch to fix the issue where pgAdmin4 was not honouring ssl mode > options. > RM#1817 > > -- > Regards, > Murtuza Zabuawala > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company

Re: [pgadmin-hackers] PATCH: To fix issue in synonym node (pgAdmin4)

2016-10-05 Thread Dave Page
Hi On Wed, Oct 5, 2016 at 9:53 AM, Murtuza Zabuawala wrote: > Hi, > > PFA patch to fix the issue in synonym node, where it was not horning parent > node while creating in different node, issue was that we were not sending > node properly. > RM#1611 That doesn't seem like a reliable way to get th

Re: [pgadmin-hackers] PATCH: To fix the issue in Debugger module (pgAdmin4)

2016-10-05 Thread Murtuza Zabuawala
Hi Dave, PFA updated patch for the same. RM#1227 Please review. -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Mon, Oct 3, 2016 at 6:05 PM, Dave Page wrote: > Hi > > On Tue, Sep 27, 2016 at 7:40 AM, Murtuza Zabuawala > wrote: > >

Re: [pgadmin-hackers] PATCH: To fix issue in synonym node (pgAdmin4)

2016-10-05 Thread Murtuza Zabuawala
Hi Dave, PFA updated patch, Added schema filter in sql. Please review. -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Wed, Oct 5, 2016 at 5:38 PM, Dave Page wrote: > Hi > > On Wed, Oct 5, 2016 at 9:53 AM, Murtuza Zabuawala > wrote:

Re: [pgadmin-hackers] pgadmin4 RPMs need some testing!

2016-10-05 Thread Olav Peeters
Hi, I posted an issue related to installing pgadmin4 on CentOS 7 via yum this morning (see: http://postgresql.nabble.com/pgAdmin4-as-web-application-on-CentOS-td5924512.html). Can you have a look at it? I'll gladly help with testing. Cheers, Olav -- View this message in context: http://postgres

Re: [pgadmin-hackers] PATCH: To fix issue in synonym node (pgAdmin4)

2016-10-05 Thread Dave Page
Hi I created a synonym from within the "dave" schema, but selected "public" (which wasn't expanded), and it placed the synonym as a direct child of "public". See the attached screenshot. On Wed, Oct 5, 2016 at 1:28 PM, Murtuza Zabuawala wrote: > Hi Dave, > > PFA updated patch, Added schema filte

Re: [pgadmin-hackers] PATCH: To fix the issue in Debugger module (pgAdmin4)

2016-10-05 Thread Dave Page
OK, that's much better. I think I've figured out what's causing the remaining execution error as well - we're not disabling the buttons until we get a response from the server, so if you click too quickly, you make multiple requests at once. I tested this by adding a "SELECT pg_sleep(2);" to a loop