Skip to content

Commit fb50412

Browse files
committed
Add mikro orm optimistic lock docs link
1 parent 652caf3 commit fb50412

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

recipes/handling-concurrency.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,3 +160,5 @@ You might have noticed that in the case of an `OptimisticLockError`, I used a cu
160160
In this scenario, we could also leverage database transaction isolation levels, like SERIALIZABLE, since this transaction does not span across multiple requests. However, there is often a requirement for long-running business processes that span multiple requests. In these situations, database transactions alone are insufficient for managing concurrency throughout such an extended business transaction. For these cases, optimistic locking proves to be a highly suitable solution.
161161

162162
You can find full working example [here](https://github.com/ikovac/teem-clone/tree/master/apps/api/src/reservation).
163+
164+
Also, If you are interested in implementing cross-request optimistic locking, check out the [MikroORM documentation](https://mikro-orm.io/docs/transactions#optimistic-locking)

0 commit comments

Comments
 (0)