Page MenuHomePhabricator

[native/web] add SQL transaction to persisting crypto module
ClosedPublic

Authored by kamil on Apr 22 2024, 4:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 23, 7:24 PM
Unknown Object (File)
Wed, Oct 23, 7:24 PM
Unknown Object (File)
Wed, Oct 23, 7:24 PM
Unknown Object (File)
Wed, Oct 23, 7:21 PM
Unknown Object (File)
Fri, Oct 18, 7:39 AM
Unknown Object (File)
Mon, Oct 14, 10:57 PM
Unknown Object (File)
Sep 4 2024, 4:38 AM
Unknown Object (File)
Sep 1 2024, 8:54 AM
Subscribers

Details

Summary

Not sure why there was no transaction here, but I think it's better to add this. Mostly because it implies more than one operation (persisting two accounts in two separate calls).

Wondering what @marcin thinks about this change.

Depends on D11720

Test Plan

Play a bit with crypto-related API to make sure it still works.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Apr 23 2024, 6:38 AM

I think it is good to add a transaction here as it will force accounts states in SQLite to be in sync.

This revision is now accepted and ready to land.Apr 24 2024, 3:21 AM