You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/runtime/optimistic-locking.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,17 +17,30 @@ If a conflict is detected—meaning someone else has modified the data since you
17
17
18
18
You can decide whether optimistic locking is enabled or disabled for your app.
19
19
20
-
## Behavior of App with Optimistic Locking Disabled
20
+
### Support Status by App Type
21
+
22
+
Optimistic locking is supported in the following types of Mendix apps:
23
+
24
+
| App Type | Support Status | Lowest Supported Version |
25
+
| --- | --- | --- |
26
+
| Online | Supported |[Studio Pro 11.5](/releasenotes/studio-pro/11.5/)|
27
+
| Offline | Supported |[Studio Pro 11.11](/releasenotes/studio-pro/11.11/)|
28
+
29
+
Additional information on optimistic locking behavior:
30
+
* In online Mendix apps, ___
31
+
* In offline Mendix apps, offline changes are synchronized to the server without being blocked by optimistic locking version checks
32
+
33
+
## App Behavior: Optimistic Locking Disabled
21
34
22
35
When two modifications are saved, they are applied in the order of processing. Only changed attributes are written to the database. This means that if the two commits change different attributes or associations of an object, the changes are not overwritten.
23
36
24
37
For example, if one user commits changes for `AttributeA` and `AttributeB` and another user commits changes for `AttributeB` and `AttributeC` for the same object, then both `AttributeA` and `AttributeC` are committed according to both users' changes. `AttributeB` is committed based on whichever change was committed later.
25
38
26
-
## Behavior of App with Optimistic Locking Enabled
39
+
## App Behavior: Optimistic Locking Enabled
27
40
28
41
The Mendix runtime implements optimistic locking by tracking the version of all objects using the attribute `MxObjectVersion` with type `Long`. Although the `MxObjectVersion` attribute is not write-protected, setting this value does not result in it being saved to the database. Its current value is compared with the value for the same object in the database.
29
42
30
-
### How to Enable and Use Optimistic Locking
43
+
### Enabling and Using Optimistic Locking
31
44
32
45
You can enable optimistic locking for your Mendix application in the `Runtime` tab in the **App Settings** dialog:
0 commit comments