We are working on a project & finding an issue while accessing the data from SQL Server.
Problem: Display of record in search console of application on number of times it has been processed.
Consider we have a record which needs to be displayed 5 times a day in search console & it has been running on client server architecture. Now the record has been displayed for 4 times in a day & then at the same moment 3 client machines request for same data at same time. So if we allow display of that data to all 3 machines & stops the processing on 2 machines ..then it will be not user friendly approach as we should stop display rather than stop the processing.
1. We can check out for concurrent request to record (can this be handled by any system or sql command ? )
2. We can display the record but not allow the processing (I don’t want this approach)
If you're in one of those predicaments where cls.__private attributes just aren't enough since they can easily be accessed through inst._cls__private, and you need something a little more secure, here's ...