[$250] [Due for payment 2025-11-20] Investigate the cannot rollback SQL issue from the nitroSQL

[mountiny]

Coming from this thread https://expensify.slack.com/archives/C05LX9D6E07/p1761670558972549?thread_ts=1761155864.690629&cid=C05LX9D6E07 cc @VickyStash

It seems like the NitroSQL does not have the transactional lock right now which can lead to [SqlExecutionError] cannot rollback - no transaction is active or [SqlExecutionError] cannot start a transaction within a transaction errors when applying merge collection and set collection at the same time.

Could you please investigate the root cause of this issue and explore options to resolve it? What would be the performance impact of introducing transaction lock to the nitro sql?

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021991982502137453839
• Upwork Job ID: 1991982502137453839
• Last Price Increase: 2025-11-21
• Automatic offers:
• situchan | Contributor | 109588340

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[chrispader]

Looking into this now! 👀

[chrispader]

PR for a fix in NitroSQLite is up here:

• feat: Migrate JS-sided locks to DatabaseQueue for transactions and executeBatch commands margelo/react-native-nitro-sqlite#227

I'll give an update tomorrow and create a Onyx bump PR

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.