Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] [ldappcng] changelog entry hierarchy ?

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] [ldappcng] changelog entry hierarchy ?

Chronological Thread 
  • From: Shilen Patel <>
  • To: Tom Zeller <>
  • Cc: Grouper Dev <>
  • Subject: Re: [grouper-dev] [ldappcng] changelog entry hierarchy ?
  • Date: Wed, 12 Oct 2011 13:19:56 +0000
  • Accept-language: en-US

The context ids for all of those changes in the change log should be the
same, so that's one way to group the changes. And you can also look up
the context id in the user audit, which will give you the high level
change only (group delete for instance).


-- Shilen

On 10/12/11 9:05 AM, "Tom Zeller"

>Given a changelog entry, is there a way to determine the "parent" change ?
>Given a deleteMembership changelog entry, can I determine that it is
>part of a group deletion ? maybe via auditing ?
>For example, for a group G with N members, deleting a group results in
>changelog entries like :
> deleteMembership M1
> deleteMembership M2
> ...
> deleteMembership MN
> deleteGroup G
>In other words, one deleteMembership changelog entry for every group
>membership at the time of group deletion before the deleteGroup
>changelog entry.
>I think it will be more real-time to just delete the group than to
>delete every membership then delete the group. Especially for large
>groups. Imagine a deployer with 10k course groups with 100k
>memberships who deletes old course groups every semester. Deleting
>each membership before deleting each group seems like extra churn.
>For OpenLDAP, the last deleteMembership will fail with a schema
>violation since the groupOfNames objectclass requires the member
>attribute. I will either need to catch the schema violation and
>replace the last member with a null value, or I will need to lookup
>the member attribute before every delete, which will slow
>Thoughts ?

Archive powered by MHonArc 2.6.16.

Top of Page