During row edit I activate "pessimistic locking" and "sync before edit", which
is doing well.
Now some customers are reporting that after a client crash (power surge,
blue screens) the locking is still active and they are not able to edit that
locked row.
Sometimes the lock is going away after some timeout but sometimes it still
exists after 20 minutes leaving the crashed client switched off.
I then use /etc/init.d/firebird restart to completely restart firebird 2.0 server to
get of that lock.

My questions:
1. Is there a way to determine, which user or workstation has initiated a
lock?
2. is there a way to manually release a lock in such a situation?

Regards
Gunther


___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de