You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If multiple connections are using the OriginPrivateFileSystemVFS with PRAGMA journal_mode TRUNCATE or PERSIST, an SQL_IOERR is likely to result. The problem is that in these modes multiple connections can open the journal file and OPFS access handles are exclusive. A workaround is not to use these modes with multiple connections.
This is not a high priority to fix right now. IDBBatchAtomicVFS is better in pretty much every way that matters to application writers - ease of integration, performance, maturity - so the OPFS VFS is mostly a proof of concept.
The text was updated successfully, but these errors were encountered:
I'm becoming more and more confident that AccessHandlePoolVFS, with a shared connection if needed, is the best approach for an OPFS VFS. Given that, I'm marking this wontfix.
If multiple connections are using the OriginPrivateFileSystemVFS with
PRAGMA journal_mode
TRUNCATE or PERSIST, an SQL_IOERR is likely to result. The problem is that in these modes multiple connections can open the journal file and OPFS access handles are exclusive. A workaround is not to use these modes with multiple connections.This is not a high priority to fix right now. IDBBatchAtomicVFS is better in pretty much every way that matters to application writers - ease of integration, performance, maturity - so the OPFS VFS is mostly a proof of concept.
The text was updated successfully, but these errors were encountered: