[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#6899) Read Entry Control response value is not compliant to definition of SearchResultEntry
- From: masarati@aero.polimi.it
- Date: Tue, 7 Jun 2011 13:33:13 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
On 06/07/2011 12:58 PM, michael@stroeder.com wrote:
> Any chance this will be fixed?
>
> It would be very handy for sync processes to get back the entryUUID generated
> by OpenLDAP of a new entry in an AddResponse without having to read the new
> entry once more.
If I get things right, what seems to be missing is a
LDAP_RES_SEARCH_ENTRY tag right before encoding the search entry,
something like
diff --git a/servers/slapd/result.c b/servers/slapd/result.c
index 0803f7f..3a21fb5 100644
--- a/servers/slapd/result.c
+++ b/servers/slapd/result.c
@@ -1042,7 +1042,8 @@ slap_send_search_entry( Operation *op, SlapReply *rs )
#endif
if ( op->o_res_ber ) {
/* read back control */
- rc = ber_printf( ber, "{O{" /*}}*/, &rs->sr_entry->e_name );
+ rc = ber_printf( ber, "t{O{" /*}}*/,
+ LDAP_RES_SEARCH_ENTRY, &rs->sr_entry->e_name );
} else {
rc = ber_printf( ber, "{it{O{" /*}}}*/, op->o_msgid,
LDAP_RES_SEARCH_ENTRY, &rs->sr_entry->e_name );
but I'd like to have some feedback.
p.