1. 28 Oct, 2022 1 commit
  2. 27 Oct, 2022 1 commit
  3. 06 Oct, 2022 1 commit
  4. 26 Sep, 2022 1 commit
  5. 13 Sep, 2022 1 commit
  6. 11 Aug, 2022 1 commit
  7. 17 May, 2022 2 commits
  8. 16 May, 2022 1 commit
  9. 11 May, 2022 1 commit
  10. 10 May, 2022 2 commits
  11. 05 May, 2022 2 commits
  12. 02 May, 2022 1 commit
  13. 23 Aug, 2021 1 commit
  14. 09 Mar, 2021 2 commits
  15. 15 Feb, 2021 1 commit
  16. 02 Nov, 2020 1 commit
  17. 20 Aug, 2020 1 commit
  18. 15 May, 2020 1 commit
  19. 18 Feb, 2020 1 commit
  20. 05 Nov, 2019 1 commit
  21. 09 Oct, 2019 2 commits
  22. 27 Jun, 2019 1 commit
  23. 13 Jun, 2019 1 commit
  24. 05 Jun, 2019 1 commit
  25. 16 Apr, 2019 1 commit
  26. 24 Jan, 2019 1 commit
  27. 23 Jan, 2019 1 commit
  28. 12 Jun, 2018 1 commit
  29. 19 Apr, 2018 1 commit
    • Côme Chilliet's avatar
      :sparkles: feat(core) Add config option to follow wildcard foreign keys · 49d6b681
      Côme Chilliet authored
      When moving a node with subnodes, like a departement, this will use a
       filter like member=* to get references, meaning it will open all groups
       and roles and other objects which may reference DNs to make sure the
       foreign key is applied and the new DN is stored.
      This will be slow if there are a lot of those objects.
      Impacted fields are member, manager, roleOccupant and owner.
      This is needed because they do not allow SUBSTR searches by schema
       definition.
      
      issue #5799
      49d6b681
  30. 05 Oct, 2017 1 commit
  31. 04 May, 2017 1 commit
  32. 06 Apr, 2017 1 commit
  33. 21 Mar, 2017 2 commits
  34. 09 Mar, 2017 1 commit