Victor Hugo M Machado wrote:if you implement something on the client that it is all the time communicating with the server .. you know when the client stops communicating on the same second, so will your "event " to capture and treat ... only that their application can be a drug .. very heavy .. maybe the client 'll be very fat
No. The script for this would actually be rather small.
The problem is that if the client detects this situation, how can it affect the database? It can't.
The solution, as already pointed out, is to make sure that the database is normalized to a consistent state upon startup, just in case it went down "dirty".