Re: [pgadmin-hackers] PATCH:Treeview item sorting (pgAdmin4)

2016-05-28 Thread Ashesh Vashi
On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > Hi, > > PFA patch, To address RM#1244. > > Now we are sorting all collection nodes based on it's labels. > The patch takes care sorting the nodes at server side. When we rename a node, or add a new no

Re: [pgadmin-hackers] [pgadmin4][PATCH][PATCH]: RM 1113: casts should be alphabetical order

2016-05-28 Thread Ashesh Vashi
Thanks - committed! -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* On Fri, May 27, 2016 at 6:44 PM, Sanket Mehta wrote: > Hi, > > Please find

[pgadmin-hackers] pgAdmin 4 commit: Fixes #1113 - Casts should be in alphabetical order.

2016-05-28 Thread Ashesh Vashi
Fixes #1113 - Casts should be in alphabetical order. Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=2fb1e96e2fc5ef0b0667298c97c0ce8c74ebcf15 Author: Sanket Mehta Modified Files -- .../servers/databases/casts/templates/cast/sql/9.1

Re: [pgadmin-hackers] PATCH: To fix the issue while adding first server (pgAdmin4)

2016-05-28 Thread Ashesh Vashi
On Fri, May 27, 2016 at 4:22 PM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > Hi, > > PFA patch to fix the issue when we add first server in pgAdmin4. > (RM#1104) > This is too hardcoded. We need a very generic resolution for this problem. i.e. Let's say - I have another serve

[pgadmin-hackers] pgAdmin 4 commit: Fixes #1143 - Update the comments in edit mode for th

2016-05-28 Thread Ashesh Vashi
Fixes #1143 - Update the comments in edit mode for the foreign data wrapper, and foreign table objects. Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=fd0d740accef4d06310f8dcbcf15fbd6f3314295 Author: Murtuza Zabuawala Modified Files -

Re: [pgadmin-hackers] PATCH: To fix issue in updating comments (pgAdmin4)

2016-05-28 Thread Ashesh Vashi
Thanks - committed! -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* On Fri, May 27, 2016 at 11:51 AM, Murtuza Zabuawala < murtuza.zabuaw...@enter

[pgadmin-hackers] pgAdmin 4 commit: Fixes #1142 - Update the comments in edit mode for th

2016-05-28 Thread Ashesh Vashi
Fixes #1142 - Update the comments in edit mode for the function, procedure, trigger function nod objects. Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=100f075510787a8d85f8d0474103167308a1e5ab Author: Murtuza Zabuawala Modified Files ---

Re: [pgadmin-hackers] PATCH: To fix issue in removing comments in edit mode (pgAdmin4)

2016-05-28 Thread Ashesh Vashi
Thanks - committed! -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* On Fri, May 27, 2016 at 11:40 AM, Murtuza Zabuawala < murtuza.zabuaw...@enter

[pgadmin-hackers] JSON serialization in pgAdmin 4

2016-05-28 Thread Lele Gaifax
Hi all, first of all, let me congratulate with you for how good pgAdmin 4 is quickly becoming. I tried it now and then, and I'm always surprised by the amount of effort you spend on it, thank you! I'd like to know if there is already a plan to properly handle date/timestamp fields, that currently

Re: [pgadmin-hackers] JSON serialization in pgAdmin 4

2016-05-28 Thread Ashesh Vashi
Hi Emanuele, On Sat, May 28, 2016 at 7:59 PM, Lele Gaifax wrote: > Hi all, > > first of all, let me congratulate with you for how good pgAdmin 4 is > quickly > becoming. I tried it now and then, and I'm always surprised by the amount > of > effort you spend on it, thank you! > Thanks! > > I'd l

Re: [pgadmin-hackers] JSON serialization in pgAdmin 4

2016-05-28 Thread Lele Gaifax
Ashesh Vashi writes: > On Sat, May 28, 2016 at 7:59 PM, Lele Gaifax wrote: >> I'd like to know if there is already a plan to properly handle >> date/timestamp >> fields, that currently fail with an error because simplejson by default >> does >> not know how the serialize (or deserialize) those d