minor changes - 5 mins OR major changes - 30 mins). If you don't like this idea what about asking the user to select a time (eg. You will need AJAX so make a countdown timer while the user is editting, and to submit the data/close the window when the timer is finished. Hopefully I will provide a new way of thinking, maybe leading to a work-around, as directly doing what you have asked is not possible to my knowledge. Someone asked a similar thing a while back and no solution. I know this is a long shot in the dark and don't expect pbmods to show up out of mystical light in the sky īut you never know :) you numbnuts might know a thing or two. I'm not looking for code, but any other ideas, solutions or ways of doing this. I guess my original statement where locking tables won't do should be changed to, locking tables can do that, is there any other way in this unforsaking state-less web. So essentially a person can be in there for an hour (It's a big page)
SCRIPTCASE EDIT RECORD BY ID UPDATE
No admin interaction needed with this.Īnd maybe even use my current Ajax functions to update the DB while that person is in the case editing page.
![scriptcase edit record by id scriptcase edit record by id](https://windows-cdn.softpedia.com/screenshots/ScriptCase_1.png)
I could also set a timer? or check to see if its been an hour since that person locked it and allow if it is. If that person is no longer available (went home), admins can go in and unlock it by force so other users now can go in. The same person that locked it however, should be able to go back in and finish and close, and hence Unlock it at that time. (Don't know where i should this save this info? another table? I already have way too many)
![scriptcase edit record by id scriptcase edit record by id](https://alternative.me/media/1280/vfront-screenshot-uhmt39vt5d7kasvm.png)
What happens if that user closes the browser or their computer turns off?įirst of all when anybody else trying to access it, it will show what user is editing it. Upon entering the case editing page, I could issue a table lock on ALL the tables for Write (there are several) and unlock it when the person leaves, closes the case and goes back to the list or elsewhere. So the case is locked for editing and should only be changed by that user.
![scriptcase edit record by id scriptcase edit record by id](https://www.scriptcase.net/docs/en_us/v9/assets/images/docs/app/comum/ligacao/ligacao_edicao/ligacao_edicao_grid.png)
I don't want another user to have pulled the same case and one of them clicks Update or Save before the other. When someone is editing a case, for example changing the persons info, editing the violations/charges they have, etc. I know how MySQL table locking works, but that won't work in my scenerio. I need to do some sort of Locking mechanism at interface level, instead of DB Level.