Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
07-03-2019 08:54 AM
07-03-2019 01:04 PM
Wouldn't just using an attribute of PlacementOrder
in the nodes work? Then as the UI reorders the list you'd have to send back to the database the queries to update the nodes and their order value. Same issue you'd have with any other database, if you're keeping an ordered list, you have to have column in your table to maintain the list order.
I suppose you could get really "graphy" and instead of an attribute you could use Prev
and Next
relationships between the nodes to create a linked-list of nodes. You'll still need to send the data back to the DB whenever the sort order changed to update the linked list order.
07-03-2019 02:11 PM
Oh damn! How did I not think of that, thanks.
All the sessions of the conference are now available online