You might consider using cayley [1] instead. If you find it easier to drop and recreate the database from scratch, then you have a source-of-record (to recreate the database from) and so it might make sense to treat your graph database as the place for doing graph analytics rather than as the place for storing the source-of-record data AND doing graph analytics.
Thinking of the graph database as a graphics programmer might think of the GPU might be a helpful perspective.
EDIT: I love dgraph, and reevaluate it anew frequently. However, I've shipped cayley and this approach works. Continue down-voting this throwaway account though.
Thinking of the graph database as a graphics programmer might think of the GPU might be a helpful perspective.
[1] https://cayley.io/ [2] https://oss.redislabs.com/redisgraph/
EDIT: I love dgraph, and reevaluate it anew frequently. However, I've shipped cayley and this approach works. Continue down-voting this throwaway account though.