When there are conflicts to a particular field (or set of cooperating fields), date isn't the only issue. Sending a conflict back to the user is only helpful if the user knows which value is right or can easily find out. In that case, who did the conflicting update might matter as well as, possibly their authority. You might also need to do some workflow analysis.
For example, if "final contract price" is being updated, and two sales team members of equal standing enter different prices, resolving the conflict might require a telephone call to the other committer. If there is more than one person in contact with the client, it might not be obvious who that is unless the conflict report tells me. On the other hand, if a person lower down discovers that their local copy has a value that is out of sync with one set by the team leader, the change might be rejected automatically, but the team leader might be sent a report just in case he or she had delegated the final decision to that team member and did want to accept the change.
In reply to Re: How to deal with data race issues with Perl?
by ELISHEVA
in thread How to deal with data race issues with Perl?
by halfbaked
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |