Hi, PFA patch to add server & client side sorting of nodes when node is renamed or newly added in tree. Bug #1244
*TODO://* 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 tree * *till parent node if we are not able to find object in parent ] * Regards, Murtuza -- Regards, Murtuza Zabuawala EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Sat, May 28, 2016 at 6:53 PM, Ashesh Vashi <[email protected] > wrote: > On Fri, May 27, 2016 at 7:34 PM, Murtuza Zabuawala < > [email protected]> 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 > <http://www.enterprisedb.com/> > > > *http://www.linkedin.com/in/asheshvashi* > <http://www.linkedin.com/in/asheshvashi> > >> >> >> -- >> Regards, >> Murtuza Zabuawala >> EnterpriseDB: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company >> >> >> -- >> Sent via pgadmin-hackers mailing list ([email protected]) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgadmin-hackers >> >> >
tree_sorting.patch
Description: Binary data
-- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
