1. 28 Apr, 2021 2 commits
  2. 31 Mar, 2021 1 commit
  3. 30 Mar, 2021 1 commit
  4. 24 Mar, 2021 2 commits
  5. 15 Mar, 2021 2 commits
  6. 10 Mar, 2021 1 commit
  7. 09 Mar, 2021 2 commits
  8. 22 Feb, 2021 6 commits
  9. 16 Feb, 2021 1 commit
  10. 11 Feb, 2021 1 commit
  11. 02 Feb, 2021 2 commits
  12. 01 Feb, 2021 1 commit
  13. 13 Jan, 2021 1 commit
  14. 12 Jan, 2021 1 commit
  15. 16 Dec, 2020 2 commits
  16. 10 Nov, 2020 3 commits
  17. 09 Nov, 2020 3 commits
  18. 06 Nov, 2020 1 commit
  19. 05 Nov, 2020 3 commits
  20. 21 Oct, 2020 1 commit
  21. 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
  22. 12 Oct, 2020 1 commit
  23. 08 Oct, 2020 1 commit