Hans Karlsen (talk | contribs) No edit summary |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
If you for some reason suspect that a third | 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 has this row cached. | 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 has this row cached. | ||
| Line 5: | Line 5: | ||
Clients will be get this information when doing their next Refresh (available via selfVM.Refresh and as framework action). | Clients will be get this information when doing their next Refresh (available via selfVM.Refresh and as framework action). | ||
The SuspectExternalUpdateInvalidate operation can made part of a bigger pattern to make MDriven play nice with others that write data. In SQLServer there is the | The SuspectExternalUpdateInvalidate operation can made part of a bigger pattern to make MDriven play nice with others that write data. In SQLServer there is the Change Tracking functionlity. Change tracking makes it possible to ask for changed rows - combine this functionality (that can be called with SqlPassthrough) and you get a system that finds changes by others and changes by triggers. | ||
Revision as of 22:01, 20 April 2018
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 has this row cached.
Clients will be get this information when doing their next Refresh (available via selfVM.Refresh and as framework action).
The SuspectExternalUpdateInvalidate operation can made part of a bigger pattern to make MDriven play nice with others that write data. In SQLServer there is the Change Tracking functionlity. Change tracking makes it possible to ask for changed rows - combine this functionality (that can be called with SqlPassthrough) and you get a system that finds changes by others and changes by triggers.