diff options
author | Nathan Kinder <nkinder@redhat.com> | 2009-02-26 21:41:15 +0000 |
---|---|---|
committer | Nathan Kinder <nkinder@redhat.com> | 2009-02-26 21:41:15 +0000 |
commit | 4124d830d825c7588029b6644afe8cbac0db9ad8 (patch) | |
tree | 7bb3b9820318cf262a12c157a9b42ad935c94059 /missing | |
parent | db2a098b97aaca733395822990cb7574e96e9135 (diff) | |
download | ds-4124d830d825c7588029b6644afe8cbac0db9ad8.tar.gz ds-4124d830d825c7588029b6644afe8cbac0db9ad8.tar.xz ds-4124d830d825c7588029b6644afe8cbac0db9ad8.zip |
Resolves: bug 487574
Bug Description: A crash occurs in the DNA plug-in when you delete an existing
value of a managed attribute.
Reviewed by: rmeggins (thanks!)
Files: see diff
Branch: HEAD
Fix Description: The DNA code was always expecting a value to be present when
processing a modify operation. The delete and replace modify operations can
be issues with no values. These operations were an oversight in the DNA code.
The fix adds cases to handle delete and replace modify operations. For a replace,
we check if we are replacing all values with nothing, and generate a new value from
the range. If we're processing a delete with no values specified, we also generate
a new value. If the delete has values specified, we check to see if the operation
leaves any values in the existing entry. If no existing values would remain after
the operation, we generate a new value.
Platforms tested: F9
Flag Day: no
Doc impact: no
Diffstat (limited to 'missing')
0 files changed, 0 insertions, 0 deletions