Possible to disable BEGIN EXCLUSIVE in WMDB native?

[scarlac]

WatermelonDB (WMDB) uses exclusive locking on the database during transactions, even when it's not explicitly enabled with the usesExclusiveLocking config flag.

This is due to the transactions being started as BEGIN EXCLUSIVE TRANSACTION, as opposed to the normal "deferred" behavior which still allows locking.
The net effect is that exclusive transactions cause other connections to fail to execute or open with the error code 5: and message database is locked. So in its default behavior, this exclusive WMDB from being used in a native + RN environment unless it's patched to support it.

Has there been any testing with it off or perhaps would it be possible to disable it and just rely on normal locking?

Code seen here:
https://github.com/Nozbe/WatermelonDB/blob/62774d5ebc4aa9ed6a2f61c8d4e795b32322cec6/native/shared/Database-sqlite.cpp#L259C7-L259C7

ie:

void Database::beginTransaction() {
    // NOTE: using exclusive transaction, because that's what FMDB does
    // In theory, `deferred` seems better, since it's less likely to get locked
    // OTOH, we don't really do multithreaded access, and when we *do*, we'd either
    // use a serial queue (easiest) or have to do a lot more work to avoid locking
    executeUpdate("begin exclusive transaction");
}

Reference reading:
https://www.sqlite.org/lang_transaction.html#deferred_immediate_and_exclusive_transactions
https://www2.sqlite.org/cvstrac/wiki?p=DatabaseIsLocked

[scarlac]

Sorry, the question is based on an invalid assumption. In WAL mode this should not be happening.