--On Tuesday, December 22, 2015 2:10 PM -0500 Michael mlstarling31@hotmail.com wrote:
I could really use some help here if anyone can sort my questions it would be greatly appreciated..I'll even through in a bundt cake and/or canned ham since it's the holidays and all.
Modifying core schema is rarely a good idea, and often frowned upon.
There are a number of reasons why doing sorting on the server side is an extremely bad idea. It's generally a much better idea to do the sorting in the client.
--Quanah
__________________________________________________
From: mlstarling31@hotmail.com To: openldap-technical@openldap.org Subject: Server Side Searching Overlay Date: Mon, 21 Dec 2015 19:27:01 -0500
So I have a request from developers to enable the sssvlv overlay. They would like the server to return sorted searches on
I enabled the overlay and then to test the functionality I added the following "ordering" rule to the core.schema.
attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' ) DESC 'RFC2256: last (family) name(s) for which the entity is known by' ORDERING caseIgnoreOrderingMatch SUP name )
The following ldapsearch works as expected and returns the "sn" attribute in alphabetical order.
ldapsearch -x -ZZ -D cn=root,dc=testlott,dc=lott -w password objectclass=person -E sss=sn sn
Based on this information I have several questions.
- Will I be violating any RFC by modifying the core.schema?
- The developers want the same functionality with the "cn" attribute. Is
this supported or even possible? 3. They also request this functionality on a couple of attributes in a custom schema. Is adding an "ordering" rule as I did with the "sn" attribute the proper way to do this?
Thanks.
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration