admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-05-07 18:44:56 +00:00
parent f2c6002ac3
commit ea3e5fee2f
4 changed files with 98 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
devdocs/specs/core-workorder.txt
View File

@@ -107,7 +107,7 @@ public class BuildingController : Controller {
If the client updates part of the wo graph, only that exact record really needs dependency checking.
There *is* however business rules that might take hold but that's all at the server and not related to concurrency directly
For example, on any change to the wo graph the server has to see if the wo is still editable and hasn't been locked or user's rights changed
But that's not strictly concurrency related in teh sense that another user change the *same* record being updated
But that's not strictly concurrency related in the sense that another user change the *same* record being updated
So, for v8 as long as it can handle a portional update to part of the graph and uses the concurrency of that exact record to check then it sidesteps a lot of multi-user scenarios
This was only an issue in v7 due to it using only the wo header itself as the source of concurrency checking which would *always* involve the whole graph in any change anywhere