Page MenuHomePhabricator

[sqlite] Add keyservers_synced_data table
ClosedPublic

Authored by michal on Mar 29 2024, 7:22 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Apr 10, 11:01 PM
Unknown Object (File)
Tue, Apr 9, 12:47 AM
Unknown Object (File)
Fri, Apr 5, 8:05 PM
Subscribers

Details

Summary

Part of ENG-6927 : Stop backing up device specific data in keyserverStore

Because we only want to back up part of keyserver store, the easiest way to implement this is to create a separate table and backup only one them. This table creates the new keyservers_synced_data table.

Depends on D11472

Test Plan

Run migration on web and native, make sure the table is created.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Mar 29 2024, 7:34 AM
Harbormaster failed remote builds in B27820: Diff 38541!

Are we sure that we will never want to inspect the content of keyserver_info values stored in keyserver_synced_data in C++? I am basically asking about the risk that we will have to manually parse JSON-strings in C++ in future.

This revision is now accepted and ready to land.Tue, Apr 2, 3:08 AM

Just for clarity - could you link diff where keyservers is added to the backup blacklist?

native/cpp/CommonCpp/DatabaseManagers/SQLiteQueryExecutor.cpp
686 ↗(On Diff #38555)

nit: this seems more readable but up to you

Rename table

Just for clarity - could you link diff where keyservers is added to the backup blacklist?

D11482

Are we sure that we will never want to inspect the content of keyserver_info values stored in keyserver_synced_data in C++?

I think we have been using this approach already and it's been working pretty well. I think it's worth it as it also makes the JS handling of data easier, and changes to schema don't require native code modifications.