On 8/3/05, Walter Meerschaert <[EMAIL PROTECTED]> wrote: > As a courtesy to my users, I wish to pop up a message thingy telling the user > when the program is waiting for the database to not be busy. Right now I > register a busy handler, and so I know how long I have been waiting, because > we have the count parameter, when it is 1, I look at the clock, when the > clock goes past 3 seconds or so it is time to tell the user tio cool his > heels while we wait for some process to commit or rollback. As far as I can > tell, there is no direct way to know when the database has begun responding > again. The busy handler simply stops being called. > > Is there a direct way I fail to see? Or, perhaps there could be an addition > to the api wherein we are told when the buy state is no more. Perhaps we > could register a no_longer_busy_handler, which could take the same parameters > as the busy handler but pass in -1 for the count.
keep trying to obtain a lock? You can set the wait time to a short value and just repeat until the user cancels or it works.
