[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: syncrepl and attribute order

Evgeniy Kosov wrote:
> On 18.07.2012 15:49, Howard Chu wrote:
>> Evgeniy Kosov wrote:
>>> On 18.07.2012 13:31, Howard Chu wrote:
>>>>> Does attribute order matter? Is it specified somehow (sorted by
>>>>> modification time?)?
>>>> No, attribute order in LDAP is unspecified.
>>> Then why does syncrepl try to reorder attributes in a backend?
>> Syncrepl aims to make an entry on the consumer identical to the entry on the
>> provider.
> The problem is that's impossible unless both backends (provider and 
> consumer) do modifications to the object the same way (e.g. move 
> modified attribute to the end of list).
> Is that (moving to the end) 
> specified somewhere?

Attribute order is unspecified. Don't ask redundant questions.

> Btw, aren't the two objects below identical in terms of LDAP/LDIF?
> dn: cn=johndoe,ou=users,o=example
> cn: johndoe
> sn: Doe
> givenName: John
> dn: cn=johndoe,ou=users,o=example
> cn: johndoe
> givenName: John
> sn: Doe


"cn=johndoe" and "cn=JohnDoe" are also identical in terms of LDAP, but
syncrepl attempts to recognize these changes as well. The design has to do
more than the specifications cover, otherwise users will complain when their
data is visually different.

>> Use delta-syncrepl instead.

> I'll have a closer look at it. Thank you.

  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/