Reversing database changes in Neo4J -

i'm developing wiki application using neo4j database. wondering is/are correct(s) procedure(s) track users edits topics mods can reverse them when needed.

i thinking saving every modified node before every change , keeping old versions couple of weeks or so, doesn't seem fast/efficient procedure.

it doesn't seem efficient method, it's method. can improve upon bit, have store old data somewhere. attach transaction handler database. whenever transaction committed, collect properties changed/removed , store them somewhere. storing modified properties, you'll save bit of space. store them in db, that's entirely you.

you use incremental backup feature, requires enterprise edition of neo4j. (which better option if possible.)

edit: transaction handler can found here. implement interface, register database using registertransactioneventhandler method in graphdatabaseservice. code called every time transaction committed (and since neo4j requires changes in transactions, it'll called time change made).

the transactioneventhandler interface bit difficult work with. data pass need, it's in odd format. if need that, feel free ask here on so. there's plenty of people (including me) that.

unfortunately, think has done in java (or jvm language, use scala). since neo4j running jvm, don't have start 1 this. also, if you're looking way data transactioneventhandler node.js, use apache thrift exact purpose.

hope helps.