[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: v2.1.30 openldap - documentDN in rdbms backend

To: hanasaki <hanasaki@hanaden.com>
Subject: Re: v2.1.30 openldap - documentDN in rdbms backend
From: Pierangelo Masarati <ando@sys-net.it>
Date: Wed, 17 Nov 2004 23:41:42 +0100
Cc: openldap-software@OpenLDAP.org
Domainkey-signature: a=rsa-sha1; s=mail; d=sys-net.it; c=simple; q=dns; b=NCb5rkepzZxpg1AalvxO5IheB64TBjw5kpcGNac23k20AXjk1P0gbSjhFASCxIgmB xLco5cuaxc72uZDySzCPQ==
References: <419BA78D.80906@hanaden.com> <419BAB3F.5060000@sys-net.it> <419BD208.5030307@hanaden.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

hanasaki wrote:

2.2.18 has the same problem.

Right, that's not been updated yet. Use the files from the CVS then, or modify the MySQL files according to those for PostgreSQL, which are fine in 2.2.18.

p.

   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497

References:
- v2.1.30 openldap - documentDN in rdbms backend
  - From: hanasaki <hanasaki@hanaden.com>
- Re: v2.1.30 openldap - documentDN in rdbms backend
  - From: Pierangelo Masarati <ando@sys-net.it>
- Re: v2.1.30 openldap - documentDN in rdbms backend
  - From: hanasaki <hanasaki@hanaden.com>

Prev by Date: Re: top objectClass not in core.schema
Next by Date: minimum upper bounds in attribute definitions
Index(es):
- Chronological
- Thread