Consider that 100-1000 or more users are trying to update the same row o fa same database and kind of like at the same time. How can accurately handle this with Wappler ?
Could set a checked-out flag upon edit call, then reset on submit action, maybe allocate a time period and if no edit within the time-frame reset the flag and timeout the user action?
1 Like
Agree with Dave, I have had to do this myself before, I just added a column to my database that was either 0 for updatable, or 1 for not allowed to update, so if a user opened record 55 and was about to edit its data, then the flag changed to 1, and if a second user tried to edit the same record it would not allow them to.
As Dave mentioned you do need to make sure there is a timer or something that sets the flag back to 0 incase a user opens the edit window, sets the flag, and then closes their browser or something.
Maybe consider setting a unique cookie per session and storing it in a database table so you know which users are active and when they are inactive set the flag back to 0.