Hans Karlsen (talk | contribs) No edit summary |
(Automatically adding template at the end of the page.) |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
If you for some reason suspect that a third party has changed rows in the database you can use selfVM.SuspectExternalUpdateInvalidate(listOfObjectsYouSuspect). | If you - for some reason - suspect that a third party has changed rows in the database, you can use [[selfVM]].SuspectExternalUpdateInvalidate(listOfObjectsYouSuspect). | ||
Doing so will notify the SyncServer (you have a sync server in MDrivenServer) that this row needs to be reread completely - by all clients that | Doing so will notify the SyncServer (you have a sync server in MDrivenServer) that this row needs to be reread completely - by all clients that have this row cached. | ||
Clients will | Clients will get this information when doing their next Refresh (available via selfVM.Refresh and as a Framework action). | ||
The SuspectExternalUpdateInvalidate operation can made part of a bigger pattern to make MDriven play nice with others that write data. | The SuspectExternalUpdateInvalidate operation can be made part of a bigger pattern to make MDriven play nice with others that write data. There is the [[SQL Server change tracking|Change Tracking]] functionality in the SQLServer. Change tracking makes it possible to ask for changed rows - combine this functionality (that can be called with [[OCLOperators sqlpassthroughobjects|SqlPassthrough]]) and get a system that finds changes by others and changes by triggers. | ||
[[Category:OCLOperators]] | |||
[[Category:OCL ViewModel Operators]] | |||
{{Edited|July|12|2024}} | |||
Latest revision as of 15:40, 10 February 2024
If you - for some reason - suspect that a third party has changed rows in the database, you can use selfVM.SuspectExternalUpdateInvalidate(listOfObjectsYouSuspect).
Doing so will notify the SyncServer (you have a sync server in MDrivenServer) that this row needs to be reread completely - by all clients that have this row cached.
Clients will get this information when doing their next Refresh (available via selfVM.Refresh and as a Framework action).
The SuspectExternalUpdateInvalidate operation can be made part of a bigger pattern to make MDriven play nice with others that write data. There is the Change Tracking functionality in the SQLServer. Change tracking makes it possible to ask for changed rows - combine this functionality (that can be called with SqlPassthrough) and get a system that finds changes by others and changes by triggers.