Igor Tandetnik wrote:
> Angus March <an...@uducat.com> wrote:
>
>> What should
>> the callback that is passed to sqlite3_busy_handler() be doing?
>>
>
> It should be deciding whether to continue waiting for the lock to clear,
> or to allow SQLite to report an error to the calling application. It
> should be conveying this decision via its return value.
>
>
>> Let's
>> say that sqlite3_reset() is called, which fails to achieve the lock.
>>
>
> sqlite3_reset doesn't take any locks.
>
>
>> After the callback has finished, what will happen with that original
>> call to sqlite3_reset()?
>>
>
> Since sqlite3_reset doesn't take any locks, a busy callback would never
> be invoked for it.
>
Well someone should tell the library on my machine that, because
it's returning locking errors
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
