Обсуждение: PATCH:Treeview item sorting (pgAdmin4)
Вложения
On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:
Hi,PFA patch, To address RM#1244.Now we are sorting all collection nodes based on it's labels.
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
--Regards,
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala <murtuza.zabuawala@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 node object, we will need to add the necessary logic at client side.--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
--Regards,
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
Вложения
Hi,PFA patch to add server & client side sorting of nodes when node is renamed or newly added in tree.Bug #1244TODO://Need a way to handle a case on client side when in object is moved out of collection.[ For time being, I've included workaround that we will close the treetill parent node if we are not able to find object in parent ]Regards,Murtuza--Regards,On Sat, May 28, 2016 at 6:53 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala <murtuza.zabuawala@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 node object, we will need to add the necessary logic at client side.--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
--Regards,
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
HiCan you please check this is still relevant, and if so, rebase it? Somehow I missed it when you first posted it :-(On Tue, May 31, 2016 at 11:06 AM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:Hi,PFA patch to add server & client side sorting of nodes when node is renamed or newly added in tree.Bug #1244TODO://Need a way to handle a case on client side when in object is moved out of collection.[ For time being, I've included workaround that we will close the treetill parent node if we are not able to find object in parent ]Regards,Murtuza--Regards,On Sat, May 28, 2016 at 6:53 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala <murtuza.zabuawala@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 node object, we will need to add the necessary logic at client side.--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
--Regards,
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave,Ashesh picked up on this task.--Regards,On Thu, Jun 23, 2016 at 3:18 PM, Dave Page <dpage@pgadmin.org> wrote:HiCan you please check this is still relevant, and if so, rebase it? Somehow I missed it when you first posted it :-(On Tue, May 31, 2016 at 11:06 AM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:Hi,PFA patch to add server & client side sorting of nodes when node is renamed or newly added in tree.Bug #1244TODO://Need a way to handle a case on client side when in object is moved out of collection.[ For time being, I've included workaround that we will close the treetill parent node if we are not able to find object in parent ]Regards,Murtuza--Regards,On Sat, May 28, 2016 at 6:53 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala <murtuza.zabuawala@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 node object, we will need to add the necessary logic at client side.--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
--Regards,
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company