Page MenuHomePhabricator

[SQLite][native] introduce `SQLiteUtils` class
ClosedPublic

Authored by kamil on Fri, Apr 11, 5:33 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 19, 4:40 PM
Unknown Object (File)
Sat, Apr 19, 2:21 PM
Unknown Object (File)
Fri, Apr 18, 11:32 PM
Unknown Object (File)
Fri, Apr 18, 11:17 AM
Unknown Object (File)
Thu, Apr 17, 3:39 PM
Unknown Object (File)
Thu, Apr 17, 10:23 AM
Unknown Object (File)
Thu, Apr 17, 2:06 AM
Unknown Object (File)
Wed, Apr 16, 11:45 PM
Subscribers

Details

Summary

There are some utility stateless functions in SQLiteQueryExecutor, that are used in various methods. This makes it impossible to move them (methods that use utilities) out of SQLiteQueryExecutor.

Because of this change here, we'll have more flexibility and we'll make things cleaner.

ENG-10538.

Test Plan

Build native app, just moving code around

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.Fri, Apr 11, 8:03 AM
kamil added inline comments.
native/cpp/CommonCpp/DatabaseManagers/SQLiteUtils.cpp
86–169 ↗(On Diff #47752)

I am considering removing at least some part of this, as this was introduced long ago to migrate to the encrypted database, and I am not sure if we still need it. It was introduced in D2874 years ago

native/cpp/CommonCpp/DatabaseManagers/SQLiteUtils.h
9–28 ↗(On Diff #47752)

This class should only do some validation, encryption, and file and PRAGMA management, not sure if this is worth documenting.

tomek added inline comments.
native/cpp/CommonCpp/DatabaseManagers/SQLiteUtils.cpp
86–169 ↗(On Diff #47752)

I think it doesn't hurt to keep it. If we have to maintain this code then removing it might be a good idea.

This revision is now accepted and ready to land.Mon, Apr 14, 1:35 AM