Hi!

Question:

Should the mgd_list_members function be fixed to return person
objects or should the client code expand the persons manually? (I
prefer the former!)

I wonder wether this bug shows also in the non-lite version of
Midgard.

How is bug fixing done? Do I send fixes to someone with write access
to cvs or something?

Currently I can't say anything about the stuff you describe (I
don't have the time to look at it today) but you can send me an
unidiff against head cvs of Midgard Lite - if you want. I will take
care of it.
OK, but before I can fix the problem, I need to know how the mgd_list_members function is supposed to work.

I suggest implementing it like the docs say:

----
Lists the persons that are members of the group with id group. Returned fields are id: id, membership ID, you won't generally have much use for this), uid, person id, name, name of person, rname, name of person in lastname,firstname format, department, department id from person, extra, the extra field from the membership table, sitegroup, sitegroup for membership record (if you have SGs)
----

I think the last part of the docs is unnecessarily redundant as is should be clear what members a person has.

We can then remove the comment by [EMAIL PROTECTED] regarding the funky behaviour. However, I fear that this could break some code. Comments anybody?

Greetings from Bonn,
Dirk


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to