Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] changelog implementation sketch

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] changelog implementation sketch

Chronological Thread 
  • From: "Tom Zeller" <>
  • To: "GW Brown, Information Systems and Computing" <>
  • Cc: "Grouper Dev" <>
  • Subject: Re: [grouper-dev] changelog implementation sketch
  • Date: Tue, 10 Jun 2008 10:49:02 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=LgltMSDFdb/sE0gpF1bc2UuPFKRCyoq9zpbHUMu3PkX6VjGqQiylPYjFh8LWm7ze02 sr/JFK+nscWQnL7aVgMzyar1Sm9cPEbf5iSBDMi3q5kuMJbkHxPZQX3ipeYbrVOiqw8i coKlSjB5FL8sKzf8Pf/LO2oLGlH3bI84yy2Jk=

On Tue, Jun 10, 2008 at 10:12 AM, GW Brown, wrote:

--On 10 June 2008 09:17 -0500 Tom Zeller <> wrote:

Representing changes from a group-centric point of view via LDIF seems
straightforward, but what about member-centrically ? e.g. how someone's
group memberships have changed.
What is the context here? Are we back to the subject id changing or is this to make it easier to query from a member point of view i.e. show me all the memberships for 'x' on a given date?

The latter, make it easier/possible to query changes from a member point of view.

If the actual change definitions  - the LDIF or whatever format we use - for a group can be queried using 'like' we could have an inefficient means of finding relevant changes which would allow us to compute a subject's memberships at a given point in time.

I agree: querying LDIF via SQL seems inefficient, perhaps even improper.

Archive powered by MHonArc 2.6.16.

Top of Page