Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
How to handle removed entity field? #723
I am sorry if this question is already asked, and I did search before asking, the most relevant one I found is: #511
We are using javers to do audits in our company, and we are satisfied with it's simplicity. However, we had an issue recently regarding a simple removal of a field in an Hibernate entity. And this field itself is an entity as well. So to simplify a bit: Product entity had a field called Category, but Category has been removed completely from db as well as from the code. If I don't do any change in the javers tables, it will break simply with the exception:
I am wondering how should we proceed in this case without cleaning up massive amount of json snapshots? I also quickly browsed in the javers source code, I could not find a place to configure ignoring removed fields..
Could you help us with some hints? Or do you need some examples to reproduce?
@bartoszwalacik Sure I am willing to contribute. Please give some hints and I will do it when it's possible. Let's frame a bit the expected behaviour if it's possible. So we should just ignore the removed fields in this case? but should we display removed ones in the changes?