>> Any suggestions how to debug and find the reason why we get SQLITE_BUSY? > Have you enabled error and warning logging? > https://www.sqlite.org/errlog.html
Thanks, I have now. > Can you enhance your existing log to report the > sqlite3_extended_errcode() value in addition to the basic error code? Yes, added! We've switched back to sqlite 3.8.10 for now to test if it was the change to 3.9.0 which makes us getting locked in SQLITE_BUSY for some reason, but I've added the above logging & extended error output so we get it in the logs if it gets locked up again.
