[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: removing global_schemacheck and SLAPD_LASTMOD flags (Was: commit: ldap/servers/slapd bconfig.c modify.c proto-slap.h schema_check.c schemaparse.c slapadd.c)
- To: kurt@OpenLDAP.org
- Subject: Re: removing global_schemacheck and SLAPD_LASTMOD flags (Was: commit: ldap/servers/slapd bconfig.c modify.c proto-slap.h schema_check.c schemaparse.c slapadd.c)
- From: Pierangelo Masarati <ando@sys-net.it>
- Date: Wed, 11 May 2005 22:52:36 +0200
- Cc: OpenLDAP Commit <openldap-devel@OpenLDAP.org>
- Domainkey-signature: a=rsa-sha1; s=mail; d=sys-net.it; c=simple; q=dns; b=mc2I3QW3rjMMqcE+nQl5cebNGws5d5LfxEGg1lBDiiGZCgX2wqOcGV0kVoDCkG9kJ +ftML5oqj1cJHUXFMzfwg==
- In-reply-to: <200505112024.j4BKOIGo014013@cantor.openldap.org>
- References: <200505112024.j4BKOIGo014013@cantor.openldap.org>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050209 LPT-Desktop/1.7.5-3.9.el3.lpt
kurt@OpenLDAP.org wrote:
bconfig.c and back-sql.
Looking at back-sql, it seems that always requiring an entry to comply
with the schema after modifications may actually be too strict if one
decides to only partially map data from LDAP to SQL. In this case, the
schema checking should be required by a database specific switch rather
than a global switch. I suggest we replace global_schemacheck with some
BACKSQL_SCHEMA_CHECK() macro. Should I go ahead?
p.
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497