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
## Create a custom conflict resolution policy using a stored procedure
132
132
133
-
These samples show how to set up a container with a custom conflict resolution policy with a stored procedure to resolve the conflict. These conflicts don't show up in the conflict feed unless there's an error in your stored procedure. After the policy is created with the container, you need to create the stored procedure. The .NET SDK sample below shows an example. This policy is supported on NoSQL Api only.
133
+
These samples show how to set up a container with a custom conflict resolution policy. This policy uses the logic in a stored procedure to resolve the conflict. If a stored procedure is designated to resolve conflicts, conflicts won't show up in the conflict feed unless there's an error in the designated stored procedure.
134
+
135
+
After the policy is created with the container, you need to create the stored procedure. The .NET SDK sample below shows an example of this workflow. This policy is supported in the API for NoSQL only.
@@ -327,7 +329,7 @@ After your container is created, you must create the `resolver` stored procedure
327
329
328
330
## Create a custom conflict resolution policy
329
331
330
-
These samples show how to set up a container with a custom conflict resolution policy. These conflicts show up in the conflict feed.
332
+
These samples show how to set up a container with a custom conflict resolution policy. With this implementation, each conflict will show up in the conflict feed. It's up to you to handle the conflicts individually from the conflict feed.
These samples show how to read from a container's conflict feed. Conflicts show up in the conflict feed only if they weren't resolved automatically or if using a custom conflict policy.
436
+
These samples show how to read from a container's conflict feed. Conflicts may show up in the conflict feed only for a couple of reasons:
437
+
438
+
- The conflict was not resolved automatically
439
+
- The conflict caused an error with the designated stored procedure
440
+
- The conflict resolution policy is set to **custom** and does not designate a stored procedure to handle conflicts
0 commit comments