1. 26 Feb, 2023 2 commits
  2. 09 Feb, 2023 1 commit
  3. 10 Nov, 2022 1 commit
  4. 08 Nov, 2022 1 commit
  5. 07 Nov, 2022 1 commit
  6. 28 Oct, 2022 1 commit
  7. 27 Oct, 2022 1 commit
  8. 06 Oct, 2022 1 commit
  9. 26 Sep, 2022 1 commit
  10. 13 Sep, 2022 1 commit
  11. 11 Aug, 2022 1 commit
  12. 17 May, 2022 2 commits
  13. 16 May, 2022 1 commit
  14. 11 May, 2022 1 commit
  15. 10 May, 2022 2 commits
  16. 05 May, 2022 2 commits
  17. 02 May, 2022 1 commit
  18. 23 Aug, 2021 1 commit
  19. 09 Mar, 2021 2 commits
  20. 15 Feb, 2021 1 commit
  21. 02 Nov, 2020 1 commit
  22. 20 Aug, 2020 1 commit
  23. 15 May, 2020 1 commit
  24. 18 Feb, 2020 1 commit
  25. 05 Nov, 2019 1 commit
  26. 09 Oct, 2019 2 commits
  27. 27 Jun, 2019 1 commit
  28. 13 Jun, 2019 1 commit
  29. 05 Jun, 2019 1 commit
  30. 16 Apr, 2019 1 commit
  31. 24 Jan, 2019 1 commit
  32. 23 Jan, 2019 1 commit
  33. 12 Jun, 2018 1 commit
  34. 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