26.11. slapi_filter_join_ex()
LDAP_FILTER_AND, LDAP_FILTER_OR, or LDAP_FILTER_NOT. When specifying the filter type LDAP_FILTER_NOT, the second filter should be NULL.
Filters of the type LDAP_FILTER_AND, LDAP_FILTER_OR, and LDAP_FILTER_NOT generally consist of one or more other filters. For example:
(&(ou=Accounting)(l=Sunnyvale)) (|(ou=Accounting)(l=Sunnyvale)) (!(l=Sunnyvale))
LDAP_FILTER_EQUALITY filters.
slapi_filter_join() function to create a new filter of the type LDAP_FILTER_AND, LDAP_FILTER_OR, or LDAP_FILTER_NOT.
#include "slapi-plugin.h" Slapi_Filter *slapi_filter_join_ex( int ftype, Slapi_Filter *f1, Slapi_Filter *f2, int recurse_always );
This function takes the following parameters:
|
ftype
| Type of composite filter you want to create. |
|
f1
| First filter that you want to join. |
|
f2
| Second filter that you want to join. If ftype is LDAP_FILTER_NOT, specify NULL for this argument. |
|
recurse_always
| Recursively joins filters f1 and f2. |
This function returns the new filter constructed from the other two filters.
The f1 and f2 filters are neither copied nor freed during the join process, but the resulting filter will have references pointing to these two filters.
slapi_filter_join() uses slapi_filter_join_ex() with recurse_always argument set to 1.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.