Hello all,
I have an application which has several screens where data is saved to different tables in an external database (Microsoft SQL Server).
Let's imagine that I have a screen to edit Books.
How can I handle 2 people (or more) editing the same book and submiting data to the DB at around the same time? Is there any best practice to deal with this scenario of user sessions? What changes should be made in the DB and how should the logic be on the OS? How does the users know that the same book is being edited at the same time?
Thank you very much in advance for your ideas on this topic.
Hi Cute Bear,
If I understand well your question, you're asking about how to handle concurrent updates.
Take a look at the documentation I shared where it is explained, step-by-step with screenshots, how to handle those scenarios.
Kind Regards,João
Hi João, thank you, that seems to be it!
I have read through the page and it seems like this would be possible as well for Reactive, even though the mentioned Forge component is for Traditional. Do you see any issues with implementing a similar logic in Reactive?
No issues. The same logic applies given that most of the logic is on the server side of things, which is the same on both Traditional and Reactive applications.
The only difference in the example is the AJAX refresh, which you don' have, nor need, in Reactive.