from what I understood is that installing a busyhandler is equivalent to use a loop around your sqlite3_step() that tests against busy state.
setting a timeout via sqlite3_busy_timeout works similar but doesn't allow to trace the busy states. please note that a LOCK state will not invoke the busy handler, as far as I know hope this helps Marcus Rick Pritchett wrote: > What I would like to do is if the data base returns a busy or locked status is > to set up my proc to retry the write. Or can I take care of this easier by > setting a long timeout? And from what I read timeout basically keeps retrying > the write for a specified amount of time. Is this correct? Or is it that the > write is retried again that time is reached? Also does sqlite use a > serialized > queue for processing the > transactions? > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Marcus Grimm, MedCom GmbH Darmstadt, Rundeturmstr. 12, 64283 Darmstadt Tel: +49(0)6151-95147-10 Fax: +49(0)6151-95147-20 -------------------------------------------------- MedCom slogans of the month: "Vacation ? -- Every day at MedCom is a paid vacation!" "Friday I have monday in my mind." "MedCom -- Every week a vacation, every day an event, every hour a cliffhanger, every minute a climax." "Damned, it's weekend again!" _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
