Bug 36028

Summary: API to get entities for all accounts
Product: Telepathy Reporter: Emilio Pozuelo Monfort <pochu27>
Component: loggerAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: low CC: nicolas
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Emilio Pozuelo Monfort 2011-04-06 08:14:10 UTC
Would be nice to have a way to get the entities for all accounts at once. One option would be to allow account=NULL in tpl_log_manager_get_entities_async(), though then we should probably add an account property to TplEntity.
Comment 1 Nicolas Dufresne 2011-04-15 11:53:38 UTC
The problem here is that an entity does not mean anything if not paired with account. Two entities might be identical, but they are not necessarily the same if not associate with that account. We need a better solution then the one you proposed.

To me the real issue is that it's not possible to get all entities (only the one from valid accounts). It's mainly related to bug #26648. We would need a way to list all the accounts (valid or not). While we could add a helper to get all the entities, this helper should allow associating the entities with an account.

We could also consider entities as Folks, but I don't know much about that library yet, and if it's really a logger task to merge the entities/logs. Meanwhile, I think having to manually query for each account is fine solution, which is the reason this request is low priority.
Comment 2 GitLab Migration User 2019-12-03 19:30:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-logger/issues/12.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.