Hi, I am currently evaluating dgraph for a company internal use case we are having. The data we want to store are graphs. An update to a node/edge/value in the graph should however not alter the node/edge/value itself but create a new version of it. From a logical point of view, this means that ev…

[image] bernd: You propose that each node points to the new version, right? (Or respectively to its predecessor). Exactly. The Edge “UPDATE” points to a new version of that node and keeps rolling. It’s like a “Ring a Ring o’ Roses”, “that does not close”. That way you would maintain a histor…

Storing and querying historical data

Users

system (system) Closed September 14, 2018, 6:42am 12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Performant node versioning Dgraph kind:question	7	898	December 23, 2020
Version controlling the graph Users	3	1113	October 28, 2017
Versioned predicates Dgraph kind:enhancement , kind:feature	3	682	August 20, 2020
How to to model this? Dgraph	0	301	December 26, 2020
DGraph storage growing too much too fast Dgraph	1	446	December 7, 2019

Storing and querying historical data

Related topics