I come from the IBM i background and have always had it easy when dealing with database record locking.
The web paradigm is very different from what I am used to and I am looking for advice on how to best handle record locks .
In our application, we usually lock the top entity from updates by others if we are updating data owned by that entity.
So for example, say we have a member file and they have an associated claims accumulator file. When we are processing a claim for said entity, we lock the member record to prevent others from processing another claim simultaneously in order to avoid a collision in the accumulator file update.
Can this be achieved in the web programming or do I need to find another way of managing record locks.