You could timestamp the data in your database. If it was updated after the moment the job was dispatched, there is a conflict.
May 20, 2019
1
Level 3
Looking for the best approach
Hi,
In my company we have a lot of background job running to update a lot of data. besides that we also have a team of data validators who update the same data in our backend system. Currently it sometime shappens that our schedled jobs update data that has manually been process by one of our team members.
basically i'm wondering what would be the best way to prevent scheduled jobs update data that has previously been adjusted by a human. I was thinking about some locking functionaly but i'm not sure what the best approach for this would be.
any ideas here?
Thanks
Please or to participate in this conversation.