5 commits

Author	SHA1	Message	Date
Petr Pchelko	7e0246a89c	Support ActorStore::newSelectQueryBuilder with query flags ... Change-Id: Ia731415f627d72811cf7a354721bb0fb28b128eb	2021-07-21 15:32:44 +00:00
daniel	806792281f	ActorNormalization should require a DB connection. ... ActorNormalization should only be used in contexts where a DB connection is already being used, or at least easily available. Bug: T276986 Change-Id: Ie8aadaffa4a30e63fcad0502d45b8ec364fc79ef	2021-03-10 21:43:49 +01:00
Petr Pchelko	1abe2e5318	Remove ActorStore::getUserIdentityByAnyId. ... Adding this method was a mistake, there's no good use for is really. Change-Id: I0b2ecee7420573092f85f4e19da731a6bd56c50b	2021-03-01 17:41:42 -07:00
Petr Pchelko	87a5cb4673	UserQueryBuilder: abstraction for actor table queries. ... This introduces a specialized SelectQueryBuilder for queries related to actor table. So far it's fairly basic, but in future it is intended to grow. This patch only introduces the new abstraction, using it will be separated into separate patches. Bug: T274223 Change-Id: Ibb1c58016e3956a46bfaf1a9f51f265114bb9ace	2021-02-22 11:47:07 -07:00
Petr Pchelko	8d2c674ab0	Introduce ActorStore, ActorLookup and ActorFactory. ... The ActorNormalization factory methods create UserIdentityValue from the database rows, either via fields of a joined table, or via a row from actor table. They assume that the actor_id exist and throw othervise. ActorNormalization is a storage-layer service providing access to finding and acquiring actor_id. The UserIdentityLookup methods do not instantiate new actor on demand, they just find an appropriate row in the actor table and return the result. Bug: T272689 Depends-On: I74d81f3f0233efb17fc8df5178e4c477cc669c6f Change-Id: Icfa1daca960c696a8cef8adab5eab53985802858	2021-02-08 10:06:46 -06:00