23 May
2013
23 May
'13
10:41 a.m.
pa@marcelot.net wrote:
On 23 mai 2013, at 16:31, Howard Chu hyc@symas.com wrote:
Don't do that.
Sure, that's why I have a *bad* workaround to not update the 'objectClass' attribute even if the original and my generated one don't match.
IMO this is not a *bad* workaround. I think it's good practice in a UI client to *not* automagically modify attribute 'objectClass' without explicit user interaction asking for modification.
Ciao, Michael.