[Date Prev][Date Next]
RE: Server Side Searching Overlay
--On Tuesday, December 22, 2015 2:10 PM -0500 Michael
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
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 ( 220.127.116.11 NAME ( 'sn' 'surname' )
DESC 'RFC2256: last (family) name(s) for which the entity is
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.
1. Will I be violating any RFC by modifying the core.schema?
2. 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?
Zimbra :: the leader in open source messaging and collaboration