On the OS standpoint, we are using multiple ones: Android, iOS and desktop
(Windows, OSX and Linux). So we need to figure a solution that works with all
these OSes.
when I used the WAL mode, I got a schema locked, while in DELETE mode i got
database locked.
>>>If WAL is supported, then you can have concurrent readers with one writer<<<
Right, but how can we get the second writer to wait until the lock is released
and continue instead of getting an error? I tries busy_timeout but that was
unsuccessful. I?d like to avoid ?locked? messages.
