1. 22 Feb, 2021 6 commits
  2. 16 Feb, 2021 1 commit
  3. 11 Feb, 2021 1 commit
  4. 02 Feb, 2021 2 commits
  5. 01 Feb, 2021 1 commit
  6. 13 Jan, 2021 1 commit
  7. 12 Jan, 2021 1 commit
  8. 16 Dec, 2020 2 commits
  9. 10 Nov, 2020 3 commits
  10. 09 Nov, 2020 3 commits
  11. 06 Nov, 2020 1 commit
  12. 05 Nov, 2020 3 commits
  13. 21 Oct, 2020 1 commit
  14. 14 Oct, 2020 1 commit
    • blam's avatar
      [contacts] Resolve phone numbers etc. to aggregate contacts rather than constituents. JB#51530 · 2e453c53
      blam authored
      Only index details for aggregate contacts. The model classes
      present aggregates rather than constituents, and same with any
      views that look up contacts for display, so the cache should
      resolve phone/email/accounts to aggregates.
      
      Constituents are only used for modifications and deletions and in
      those cases they should be referred to by ID instead of via detail
      resolution lookup.
      2e453c53
  15. 12 Oct, 2020 1 commit
  16. 08 Oct, 2020 3 commits
  17. 07 Oct, 2020 2 commits
  18. 06 Oct, 2020 2 commits
  19. 02 Oct, 2020 1 commit
  20. 25 Sep, 2020 1 commit
  21. 24 Sep, 2020 3 commits
    • chriadam's avatar
      5a725b74
    • chriadam's avatar
      Performance: reduce the detail types fetched during populate step · de4d5184
      chriadam authored
      All details other than timestamp and status flags were moved out
      of the main contacts table in qtcontacts-sqlite recently.
      This means that it is relatively expensive to query detail types
      such as gender/favorite/synctarget etc if they are not required.
      
      Note that we still fetch the gender when populating the "all" list,
      as we can use this data when determining valid merge targets.
      de4d5184
    • blam's avatar
      [contacts] Use cache display label where possible. JB#50658 · 6c222eb0
      blam authored
      In the past, display names were not typically set in QContactDisplayLabel
      so SeasidePerson had to calculate a display label. This is no longer
      the case, so the QContactDisplayLabel value should be preferred.
      
      In cases where the cache item does not exist (e.g. a temporary
      contact not saved to db), SeasidePerson still needs to calculate the
      display label.
      6c222eb0