Bug #129
Saving ordered values don't keep order
| Status: | Closed | Start: | 16/01/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | - | Spent time: | - | |
| Target version: | 0.6 |
Description
When saving ordered values (with X-ORDERED extension), eg. olcAccess values, order is not correctly saved, due to imprecise specification.
See http://www.openldap.org/its/index.cgi/Incoming?id=7110 for the corresponding bug in OpenLDAP, but this risk not to be fixed.
The problem is that LinID send values with the right index but not in the right order. Eg:
attr: {2} value2
attr: {0} value0
attr: {1} value1
instead of:
attr: {0} value0
attr: {1} value1
attr: {2} value2
Related issues
| related to Directory Manager - Bug #130: Fix ordering of ordered values | Closed | 16/01/2012 |
History
Updated by Raphael Ouazana 4 months ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Fixed in DM #130.
Updated by Raphael Ouazana 4 months ago
- Target version changed from 0.5 to 0.6
- % Done changed from 100 to 90
Reopened, see #130.