Hi,
I changed recently from sluprd to syncrepl. And I saw that the syncrepl do not preserve the order of the value on multivalued attribute (I dont know if it is a bug) .
Example:
Entry on LDAP master/slave:
dn: cn=ricardo deliveryProgramPath: odeiavir deliveryProgramPath: maildrop
When I do this modify on master:
dn: cn=ricardo changetype:modify replace: deliveryProgramPath deliveryProgramPath: maildrop deliveryProgramPath: odeiavir
The result is:
LDAP Master:
dn: cn=ricardo deliveryProgramPath: maildrop deliveryProgramPath: odeiavir
LDAP Slave:
dn: cn=ricardo deliveryProgramPath: odeiavir deliveryProgramPath: maildrop
The slave server keep the old order. Someone knows if this is a replication bug ?
Thanks, Ricardo Machini
Ricardo Machini wrote:
Hi,
I changed recently from sluprd to syncrepl. And I saw that the syncrepl do not preserve the order of the value on multivalued attribute (I dont know if it is a bug) .
Attributes in LDAP are *sets* of values. Sets have no ordering property, therefore order is irrelevant.
openldap-technical@openldap.org