Pavel Ivanov wrote:
>> Will sqlite3_unlock_notify() work for this, or do I need to be
>> doing something else?
>>
>
> No, sqlite3_unlock_notify() doesn't work for multi-process
> applications. For them you should do some retries after delay by
> yourself (probably using sqlite3_busy_handler() ) or use
> sqlite3_busy_timeout().
>
>
Yes, it looks like the answer involves sqlite3_busy_handler(). I
take it I don't need that shared cache stuff or whatever. I'm having a
hard time understanding how I'm supposed to use it though. What should
the callback that is passed to sqlite3_busy_handler() be doing? Let's
say that sqlite3_reset() is called, which fails to achieve the lock.
After the callback has finished, what will happen with that original
call to sqlite3_reset()?
I'd appreciate it if someone could give me some quick and dirty
pseudocode to illustrate what I should be doing.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
