Bug #91
syncoptions: if a default_value is specified, the create_value is lost
| Status: | Closed | Start: | 26/06/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Jonathan Clarke | % Done: | 100% |
|
| Category: | Core | |||
| Target version: | 1.1.0 | |||
| Problem in version: |
Description
Consider this extract of lsc.properties:
lsc.syncoptions.ldap2ldapTestTask.telephoneNumber.create_value = "000000", "11111" lsc.syncoptions.ldap2ldapTestTask.telephoneNumber.default_value = "123456", "789987"
This causes entries to be created with:
telephoneNumber: 123456 telephoneNumber: 789987
However, the correct behaviour would be to create with:
telephoneNumber: 000000 telephoneNumber: 11111
Then, upon modifying change these values.
It is unclear why one would want to do this anyway, but still, a fix is coming :)
Associated revisions
Fixes #91. Don't override create_value with default_value
History
Updated by Jonathan Clarke about 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset r275.
Updated by Jonathan Clarke about 1 year ago
- Status changed from Feedback to Closed
Fixed, closing issue.