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

Re: Unexpected Attribute Behavior

To: openldap-software@openldap.org
Subject: Re: Unexpected Attribute Behavior
From: Buchan Milne <bgmilne@staff.telkomsa.net>
Date: Mon, 12 Nov 2007 12:47:24 +0200
Cc: Kevin Burnett <kburnett61@gmail.com>
Content-disposition: inline
In-reply-to: <f2c191170711091246i5a92cf52o9543a62aea18ccc@mail.gmail.com>
References: <f2c191170711091246i5a92cf52o9543a62aea18ccc@mail.gmail.com>
User-agent: KMail/1.9.6

On Friday 09 November 2007 22:46:10 Kevin Burnett wrote:
> I am implementing an OpenLDAP installation that utilizes inetOrgPerson
> as the main user structure with roughly forty attributes that may be
> used with each user. Of the forty attributes, I have added a custom
> schema which includes 15 custom attributes. I am using MySQL 5 as the
> backend via backsql.

As the problem you describe is obviously related to the use of back-sql, is 
there a specific reason you are using back-sql, or just because you think it 
is convenient? If there is no specific reason, you may wish to reconsider, as 
back-sql is not as well supported, feature rich, or anywhere near as fast as 
the primary (bdb, hdb) backends, where most likely you would not have 
experienced any problems that you are experiencing here.

Regards,
Buchan

References:
- Unexpected Attribute Behavior
  - From: "Kevin Burnett" <kburnett61@gmail.com>

Prev by Date: Re: enabling uid and userPassword attributes
Next by Date: Re: strict ldif check
Index(es):
- Chronological
- Thread