于 Wed, 13 Jun 2007 11:24:43 -0300 Jeronimo Zucco jczucco@ucs.br 写道:

Hi, Zhang.

Did you try it with valsoft overlay ?

http://www.openldap.org/faq/data/cache/1282.html

and

man 5 slapo-valsort

Actually I didn't try, but I did came across it and read its manual. I am not sure if it addresses my problem, so far it seems to be used for sorting values between multiple values of a single attribute while in my case I am sorting entries based on certain (actually one, modifyTimeStampe) attribute.

Zhang Weiwu escreveu:

...

Dear list

As the project I am working on requires, all ldap search results should return latest-modified entry first. This requirement have many practical reason behind it and is an important requirement. I solve this problem by always invoke ldap search with 'sort' option.

I believe by doing so I have lowered down performance, especially the search result is often several thousands records. Now the server is overburden. I have noticed if I don't use sort feature, the result is always the reverse of the project requirement: last modified entries are displayed last. (project requirement is: last modified entries are displayed first.)

The project requirement will not likely to change in a few years time, so I think perhaps we can enhance performance by reconfiguring openldap to reverse sort order -> not possible on OpenLDAP itself but I guess probably by configuring BDB backend, to ask it to 'save' data in the opposite way, and by doing so make future search result automatically 'sorted'. So far, it's my dream and my wild guess. I am digging into BDB documents to find out if such configuration is possible and also write the list see if experts knows this possibility already.

And, I wouldn't be surprised if BDB cannot be configured the way I like, but, it's stupid not to ask the list just in case if it's possible

Thanks a lot in advance!

于 Wed, 13 Jun 2007 12:28:06 -0700 Howard Chu hyc@symas.com 写道:

Zhang Weiwu wrote:

...

Dear list

As the project I am working on requires, all ldap search results should return latest-modified entry first. This requirement have many practical reason behind it and is an important requirement. I solve this problem by always invoke ldap search with 'sort' option.

I believe by doing so I have lowered down performance, especially the search result is often several thousands records. Now the server is overburden. I have noticed if I don't use sort feature, the result is always the reverse of the project requirement: last modified entries are displayed last. (project requirement is: last modified entries are displayed first.)

That must be pure coincidence. Entries are returned in their order of creation, not order of modification. There is no configuration that will change this ordering.

I don't think it's pure coincidence, at least not 'pure'. I tried to modify an entry in middle of the search result, and do search again, this very entry goes to the bottom of the search result.