Issue #80 has been updated by Cl?ment Oudot.
Jonathan Clarke wrote: > This should indeed work (although you don't need the cast to (Boolean)). > > However, it doesn't take into account the case where the modrdn condition is > something more complex that needs evaluating, and ends up being false. We > really should fully interpret the contents of the condition here, to be > consitent. Hello, I have a suggestion: we can test the 'dn' rule. If this rule is empty, this mean that we do not want to manage DN. In this case, we never check modrdn and go direct in update. What do you think? ---------------------------------------- Feature #80: Force LSC to apply modifications if modrdn is false http://tools.lsc-project.org/issues/show/80 Author: Cl?ment Oudot Status: New Priority: Normal Assigned to: Category: Target version: Hello, I use a connector in "update-only" mode. So I set to false create/delete/modrdn conditions. I do not use "dn" rule because I cannot set this rule (I don't know how the destination entries will be named). I just want to update an attribute in the destination entry (I know how to mach source entry and destination entry with a filter). LSC see that my destination entry DN is not correct, so it tries to make a modrdn. My modrdn is false so it does nothing. But it does not do the update! Indeed, LSC is programmed to skip update i modrdn is required. But if modrdn condition is false, update should be made. Are you agree? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090615/0b49402e/attachment.htm>
