Page MenuHomePhabricator

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

Authored by kamil on Mon, Apr 22, 4:01 PM.
Tags
None
Referenced Files
F1696510: D11721.id39614.diff
Fri, May 3, 1:37 PM
F1693503: D11721.id39372.diff
Thu, May 2, 3:47 PM
F1693411: D11721.id.diff
Thu, May 2, 3:26 PM
Unknown Object (File)
Sun, Apr 28, 4:17 PM
Unknown Object (File)
Fri, Apr 26, 7:59 PM
Unknown Object (File)
Fri, Apr 26, 1:27 PM
Unknown Object (File)
Tue, Apr 23, 1:50 AM
Unknown Object (File)
Tue, Apr 23, 1:49 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.Tue, Apr 23, 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.Wed, Apr 24, 3:21 AM