| | |
| | | allows clients to find people even when they misspell names as in the |
| | | following example.</para> |
| | | |
| | | <screen>$ ldapsearch --baseDN dc=example,dc=com "(cn~=Babs Jansen)" cn |
| | | <screen>$ ldapsearch --port 1389 --baseDN dc=example,dc=com "(cn~=Babs Jansen)" cn |
| | | dn: uid=bjensen,ou=People,dc=example,dc=com |
| | | cn: Barbara Jensen |
| | | cn: Babs Jensen</screen> |
| | |
| | | the search filter. An equality index requires clients to match values |
| | | without wildcards or misspellings.</para> |
| | | |
| | | <screen>$ ldapsearch --baseDN dc=example,dc=com "(uid=bjensen)" mail |
| | | <screen>$ ldapsearch --port 1389 --baseDN dc=example,dc=com "(uid=bjensen)" mail |
| | | dn: uid=bjensen,ou=People,dc=example,dc=com |
| | | mail: bjensen@example.com</screen> |
| | | </section> |
| | |
| | | |
| | | <para>The following example shows a search that specifies ranges.</para> |
| | | |
| | | <screen>$ ldapsearch |
| | | --baseDN dc=example,dc=com |
| | | "(&(uidNumber>=1120)(roomNumber>=4500))" |
| | | uid |
| | | <screen>$ ldapsearch --port 1389 --baseDN dc=example,dc=com |
| | | "(&(uidNumber>=1120)(roomNumber>=4500))" uid |
| | | dn: uid=charvey,ou=People,dc=example,dc=com |
| | | uid: charvey |
| | | |
| | |
| | | attribute is indexed for presence by default to allow quick retrieval |
| | | of entries with ACIs.</para> |
| | | |
| | | <screen>$ ldapsearch --baseDN dc=example,dc=com "(aci=*)" - |
| | | <screen>$ ldapsearch --port 1389 --baseDN dc=example,dc=com "(aci=*)" - |
| | | dn: dc=example,dc=com |
| | | |
| | | dn: ou=People,dc=example,dc=com</screen> |
| | |
| | | in the filter. Substring indexes can be expensive to maintain, especially |
| | | for large attribute values.</para> |
| | | |
| | | <screen>$ ldapsearch --baseDN dc=example,dc=com "(cn=Barb*)" cn |
| | | <screen>$ ldapsearch --port 1389 --baseDN dc=example,dc=com "(cn=Barb*)" cn |
| | | dn: uid=bfrancis,ou=People,dc=example,dc=com |
| | | cn: Barbara Francis |
| | | |