# Concurrent db changes

**URL:** <https://forum.bubble.io/t/concurrent-db-changes/228164>\
**Category:** Database\
**Created:** [October 13, 2022, 7:23am UTC](https://forum.bubble.io/t/concurrent-db-changes/228164 "2022-10-13T07:23:58Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![gf\_wolfer](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/gf_wolfer/32/262456_2.png) [@gf\_wolfer](https://forum.bubble.io/u/gf_wolfer)\
**Post date:** [October 18, 2022, 1:37pm UTC](https://forum.bubble.io/t/concurrent-db-changes/228164/10 "2022-10-18T13:37:25Z")

</div>

One can dream…

> [@Concurrency & Transactionality updates coming in Bubble?](http://forum.bubble.io/t/concurrency-transactionality-updates-coming-in-bubble/194356/6):
>
> No updates unfortunately confused This is an area under active discussion though as we are prioritizing projects for Q4/Q1… Will keep y’all posted.

This has been a nagging problem for a number of years. I have a number of customers with popular Events that sell out in minutes and it always leads to issues

@NigelG the cart lock is effectively what most Ticketing systems do and then release it after X minutes if the transaction is not completed, but having even tried that in Bubble that first click to add to the cart (or ‘proceed with order button’ in my case) can lead to a race condition / inconsistency.

Happy to pay for a good solution here if someone can come up with something that consistently works with about 60 concurrent users going after the same 20 stock items

---

_[View the full topic](https://forum.bubble.io/t/concurrent-db-changes/228164)._