[pgadmin-hackers] [pgAdmin4][Patch] Minor fix in test file for the Template loader

2017-01-30 Thread Murtuza Zabuawala
Hi, PFA patch to fix the issue in test suite for template loader. *Issue(Python3):* murtuza@vm:~/pgadmin4/web/regression$ python3 runtests.py pgAdmin 4 - Application Initialisation == The configuration database - '/../.pgadmin/test_pgadmin4.db' does not exist

Re: [pgadmin-hackers] [pgAdmin4][PATCH] To fix the issue in handling of timestamp type

2017-01-30 Thread Murtuza Zabuawala
Hi Dave, PFA updated patch. -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Mon, Jan 30, 2017 at 8:07 PM, Dave Page wrote: > Can you rebase this please? > > Thanks. > > On Mon, Jan 30, 2017 at 5:37 AM, Murtuza Zabuawala > wrote: > >

Re: [pgadmin-hackers] Acceptance Tests against a browser (WIP)

2017-01-30 Thread Atira Odhner
Here's the patch with one more fix -- cleaning up the connections that get created in pgAdmin. On Mon, Jan 30, 2017 at 2:28 PM, George Gelashvili wrote: > so, it sounds like you're saying our accaptable_test_db is unacceptable :-P > > here's a patch that takes an "--exclude" flag (see README) a

Re: [pgadmin-hackers] Acceptance Tests against a browser (WIP)

2017-01-30 Thread George Gelashvili
so, it sounds like you're saying our accaptable_test_db is unacceptable :-P here's a patch that takes an "--exclude" flag (see README) and doesn't create dbs that don't get cleaned up afterwards On Fri, Jan 27, 2017 at 11:28 AM, Dave Page wrote: > On Fri, Jan 27, 2017 at 4:11 PM, Dave Page wro

Re: [pgadmin-hackers][Patch] Bypass recovery state for Greenplum

2017-01-30 Thread Dave Page
Thanks - committed! On Mon, Jan 30, 2017 at 4:16 PM, Atira Odhner wrote: > Whoops we accidentally left in hardcoded db config we used for running tests > from our IDE. > > Here's a fixed patch. > > On Mon, Jan 30, 2017 at 6:45 AM, Dave Page wrote: >> >> Hi >> >> On Fri, Jan 27, 2017 at 5:18 PM,

[pgadmin-hackers] pgAdmin 4 commit: Bypass recovery checks with older servers. This is re

2017-01-30 Thread Dave Page
Bypass recovery checks with older servers. This is required for Greenplum which is based on PG 8.3 at present. Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=c6b67fc66a40d477be06ac743af63c71aeb952fd Author: Atira Odhner Modified Files --

Re: [pgadmin-hackers][Patch] Bypass recovery state for Greenplum

2017-01-30 Thread Atira Odhner
Whoops we accidentally left in hardcoded db config we used for running tests from our IDE. Here's a fixed patch. On Mon, Jan 30, 2017 at 6:45 AM, Dave Page wrote: > Hi > > On Fri, Jan 27, 2017 at 5:18 PM, George Gelashvili > wrote: > > This bypasses checking if the DB is in recovery for versio

Re: [pgadmin-hackers][Patch] Refactor sql template version picking

2017-01-30 Thread Atira Odhner
Awesome. Thanks folks! On Mon, Jan 30, 2017 at 6:35 AM, Fahar Abbas wrote: > Sure Dave. > > On Mon, Jan 30, 2017 at 4:33 PM, Dave Page wrote: > >> Thanks Murtuza. Fixed and committed. George; I stuck with the original >> filename for the loader - I couldn't come up with anything better. >> >> F

Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM#2015 - Trigger issues

2017-01-30 Thread Dave Page
For the record, the author was Neel, not Murtuza as I put in the commit message. Sorry Neel! On Mon, Jan 30, 2017 at 1:06 PM, Dave Page wrote: > Thanks, patch applied. > > On Fri, Jan 27, 2017 at 7:06 PM, Neel Patel > wrote: >> Hi, >> >> Please find attached patch file for the fix of RM#2015.

Re: [pgadmin-hackers] [pgAdmin4][PATCH] To fix the issue in handling of timestamp type

2017-01-30 Thread Dave Page
Can you rebase this please? Thanks. On Mon, Jan 30, 2017 at 5:37 AM, Murtuza Zabuawala wrote: > Hi, > > Please find a patch to fix the issue in timestamp & time type when user > tries to provide scale/lengt to them. > I did some refactoring in code to handle it at one place, affected nodes > wou

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

2017-01-30 Thread Dave Page
Hi On Mon, Jan 30, 2017 at 5:31 AM, Murtuza Zabuawala wrote: > Hi Dave, > > Please find updated patch, Tested against maintenance database as well. I can change parameters on the maintenance DB now, but it still crashes if I try to change the comment. Both operations on other databases seem to w

[pgadmin-hackers] pgAdmin 4 commit: Ensure dialogues cannot be moved under the navbar. Fi

2017-01-30 Thread Dave Page
Ensure dialogues cannot be moved under the navbar. Fixes #2047 Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=30e546208fa4ac91bbe1759e3981522158ee703e Author: Surinder Kumar Modified Files -- web/pgadmin/static/css/overrides.css |

Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM2047 - Allow user to move panel over the menu bar

2017-01-30 Thread Dave Page
Thanks, patch applied. On Mon, Jan 30, 2017 at 5:09 AM, Surinder Kumar wrote: > Hi Dave, > > Solution: > Setting z-index: 10 of .pg-navbar menu class to allow panel float over the > menu bar. > > Please find attached patch. > > Thanks, > Surinder Kumar > > > -- > Sent via pgadmin-hackers mailing

Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM#2015 - Trigger issues

2017-01-30 Thread Dave Page
Thanks, patch applied. On Fri, Jan 27, 2017 at 7:06 PM, Neel Patel wrote: > Hi, > > Please find attached patch file for the fix of RM#2015. > > Below additional issues are fixed along with description provided in RM. > > When user update any of the parameter - trigger gets disappear from browser

[pgadmin-hackers] pgAdmin 4 commit: Resolve various trigger issues. Fixes #2015

2017-01-30 Thread Dave Page
Resolve various trigger issues. Fixes #2015 - Allow changing of row/statement flag - When user update any of the parameter - trigger gets disappear from browser tree. To make it visible user has to do refresh. - Edit Mode - 'Row level' trigger was not allowed to edit for "inline edb-spl" trigge

Re: [pgadmin-hackers] [pgAdmin4][Patch]: RM 2069 - Wrong tablespace displayed in table properties

2017-01-30 Thread Dave Page
Hi Can you rebase this please? Thanks. On Fri, Jan 27, 2017 at 11:53 AM, Khushboo Vashi wrote: > Hi, > > Please find the attached updated patch. > > Thanks, > Khushboo > > On Fri, Jan 20, 2017 at 5:31 PM, Dave Page wrote: >> >> On Fri, Jan 13, 2017 at 6:41 AM, Khushboo Vashi >> wrote: >> > Hi

Re: [pgadmin-hackers] [pgAdmin4][Patch]: Fix RM1790 - [Web] Support setting a field's value to "null"

2017-01-30 Thread Dave Page
On Fri, Jan 27, 2017 at 10:32 AM, Surinder Kumar wrote: > Hi Dave, > > Please find updated patch. > > On Mon, Jan 16, 2017 at 10:01 PM, Dave Page wrote: >> >> Hi >> >> On Fri, Jan 13, 2017 at 9:24 AM, Surinder Kumar >> wrote: >> > Hi >> > >> > Please find attached patch and review. >> > >> > On

Re: [pgadmin-hackers] [pgAdmin4][patch][FileManager]: RM-2110 - Invalid path error displayed

2017-01-30 Thread Dave Page
Hi On Fri, Jan 27, 2017 at 10:30 AM, Neel Patel wrote: > Hi, > > Please find attached patch file for the fix of RM#2110. > > When user try to save the file through fileManager then it gives error > saying "Invalid Path" while getting folder details from python server. This > issue is only reprodu

Re: [pgadmin-hackers][Patch] Bypass recovery state for Greenplum

2017-01-30 Thread Dave Page
Hi On Fri, Jan 27, 2017 at 5:18 PM, George Gelashvili wrote: > This bypasses checking if the DB is in recovery for versions of postgres > that don't support pg_is_in_recovery() (anything pre-9.0, such as > Greenplum). > > This patch depends on the "Refactor sql template version picking" patch. T

Re: [pgadmin-hackers][Patch] Refactor sql template version picking

2017-01-30 Thread Fahar Abbas
Sure Dave. On Mon, Jan 30, 2017 at 4:33 PM, Dave Page wrote: > Thanks Murtuza. Fixed and committed. George; I stuck with the original > filename for the loader - I couldn't come up with anything better. > > Fahar; This is a fairly major change. Please test thoroughly on > different versions of P

[pgadmin-hackers] pgAdmin 4 commit: Create a template loader for SQL templates.

2017-01-30 Thread Dave Page
Create a template loader for SQL templates. This will automatically find the correct version of a template for the server version, and allows us to remove templates that were previously duplicated for different server versions. Patch by George & Tira at Pivotal. Review by me and Murtuza from ED

Re: [pgadmin-hackers][Patch] Refactor sql template version picking

2017-01-30 Thread Dave Page
Thanks Murtuza. Fixed and committed. George; I stuck with the original filename for the loader - I couldn't come up with anything better. Fahar; This is a fairly major change. Please test thoroughly on different versions of PG and EPAS to ensure that the correct SQL templates are being used. They'

Re: [pgadmin-hackers] [pgAdmin4] [PATCH] Simplify Server's python setup

2017-01-30 Thread Dave Page
On Sat, Jan 28, 2017 at 1:00 AM, Jan Alexander Steffens wrote: > On Fri, Jan 27, 2017 at 5:56 PM Dave Page wrote: >> >> On Fri, Jan 27, 2017 at 1:37 PM, Jan Alexander Steffens >> wrote: >> > I did mean Py_SetPath, not PySys_SetPath. >> >> Ah, OK - it wouldn't compile with that (Python 2 :-/ ) so

Re: [pgadmin-hackers] [pgAdmin4] [PATCH] Simplify Server's python setup

2017-01-30 Thread Jan Alexander Steffens
On Fri, Jan 27, 2017 at 5:56 PM Dave Page wrote: > On Fri, Jan 27, 2017 at 1:37 PM, Jan Alexander Steffens > wrote: > > I did mean Py_SetPath, not PySys_SetPath. > > Ah, OK - it wouldn't compile with that (Python 2 :-/ ) so I assumed it > was a typo. > > > Unfortunately, after checking > > again