Closed avnerbarr closed 2 years ago
SQLite blocks the file when you access it. You need to keep a global reference to the connection to avoid this kind of issues. On another matter of things, this repo is abandoned. The Author is involved in some kind of online teaching courses and even though he has activity on other repos he seems to not have the courage to announce he will not be continuing with this one. My advice is that you switch to another library like GRDB.
We merged a fix replacing the try!
by a try?
.
@NathanFallet I am still getting this crash on the latest release 0.14.1. It appears the try?
you mention is still a try!
, so this is still an issue.
@tw0po1nt We reverted this fix; as explained in #1075, you should use failableNext()
and handle the error by yourself using a do
/catch
block. We cannot provide a default behavior (e.g. return nil) when an error occurs, it's up to you to choose what you want to do.
getting a crash here when the DB is open in 2 processes: