I am considering the possibility of keeping history of all the data changes on a OrientDB database. This history shall be explorable just like the normal data. Like: I shall be able to query all the changes that a user have ever done to his profile.
I considered some solution like suggested here to create history classes for each vertex class and to create a history record for each update (vertex version increase) in that class whenever a vertex changes.
Can this be done directly inside DB using some kind of trigger like what Oracle has?
Even if that served for normal data of vertex what about edges? how could I preserve them in history? and between vertices?
I there a more straight forward way to do this in OrientDB?