Table of Contents
Advertisement
Handling Extensible Match Filters
The server checks the value returned by the filter matching function:
If the entry matches the filter, the server verifies that the entry is in the scope of
4.
the search before returning the entry to the LDAP client as a search result.
Query Operators in Matching Rules
As mentioned in "How the Server Handles the Filter" on page 135, the server uses
a query operator when searching the index for possible candidates.
Note that this applies to the
own back-end or if you have not set up indexing by matching rules, the server does
not make use of the query operator.
The server checks the value of the
to determine which operator is specified. The following table lists the possible
values for this parameter.
Table 11-3
Operator
SLAPI_OP_LESS
SLAPI_OP_LESS_OR_EQUAL
SLAPI_OP_EQUAL
SLAPI_OP_GREATER_OR_EQUAL
SLAPI_OP_GREATER
136
Netscape Directory Server Plug-In Programmer's Guide • December 2003
The server calls the filter matching function (which is specified in the
SLAPI_PLUGIN_MR_FILTER_MATCH_FN
object, the entry, and the attributes of the entry.
If the entry does not match but the search request also specifies that the
attributes in the DN should be searched, the server calls the filter matching
function again, passing in the filter object, the entry, and the attributes in
the DN.
If the function returns 0, the entry matched the search filter.
If the function returns -1, the entry did not match the search filter.
If the function returns an LDAP error code (a positive value), an error
occurred.
ldbm
Query Operators in Extensible Match Filters
parameter), passing in the filter
default back-end database. If you are using your
SLAPI_PLUGIN_MR_QUERY_OPERATOR
Description
<
<=
=
>=
>
parameter
Advertisement
Table of Contents
