Re: Queries fail after canceling query when using subordinate back-sql db (ITS#2999)

[gst@sysfrog.org]

--=-0DWAbvmyAXan+yTQ0N0N
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2004-03-05 at 08:54, Pierangelo Masarati wrote:

Hello Pierangelo,

> The problem is fixed now in HEAD code;
> I need to check if the fix doesn't break
> anything else before bringing it to
> release.  Please check.

Wow, thanks for the really _fast_ fixing of this problem, back-ldbm +
back-sql work fine now.

I still got another similiar problem when using back-ldap together with
a subordinate back-sql database. The difference is, that all subsequent
queries fail, no matter if i cancel the ldapsearch or not.

To reproduce this problem:

*) Setup a remote ldap server with c=3DRU as Root and add one OU entry.

*) Replace the ldbm section from the slapd.conf which i attached to this
bugreport with:

database       ldap
uri            ldap://some.remote.server/
suffix         "c=3DRU"

*) Do a "ldapsearch -b "c=3DRU". The first query works fine, after this it
just returns "search: 2, result: 32 No such object."

If i comment out the back-sql stuff and only use the ldap database
everything works fine.

I haven't opened a new report, because i'm not sure if this problem is
related to the previous one.

cu
/gst


--=-0DWAbvmyAXan+yTQ0N0N
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBASMLnZtF7I/+gjcERAhYJAJ9cfXtyjJgVSfh0YWi866bNqN6BvgCglkqG
p4kz2MgZdN8A6PExADw4bKU=
=+HW3
-----END PGP SIGNATURE-----

--=-0DWAbvmyAXan+yTQ0N0N--