On 01/10/2018 10:08 AM, Máirín Duffy wrote: > Hi William, > >> With displayname you can only sort by "order of the displaynames". >> So we can at least consistently sort this given the scenario above! > > Imagine a phone book sorted this way. In the US in any given town > there would be 50 pages of Johns, making wayfinding really difficult. > Is there a way for an application that's using LDAP in the backend to > pull the last substring, for example, if they wanted to use the > heuristic of last ordered is the sorting key? > >> To *search* for surnames however, now you can do a substring search >> in the displayName field. I'm not sure of your LDAP profficency, but >> the search would be: > > I'm really not proficient at all. Is this like a regexp so "=*Brown" > matches any entries that end in "Brown"? This is common, and you would use a "substring" search filter: "(sn=*brown)" > Would this miss someone who had two surnames, say Sally Brown West, > who chooses not to hyphenate? "(sn=*brown*)" You can also use compound search filters too: Here is an "or" filter: "(|(legalname=*brown*)(cn=*brown*")(sn=*brown*))" The options are endless. Regards, Mark > > Cheers, > ~m > _______________________________________________ > 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
