[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: back-sql using varchar keyvals and ids
- To: "Pierangelo Masarati" <ando@sys-net.it>
- Subject: RE: back-sql using varchar keyvals and ids
- From: "Potkanski, Jason" <JPotkanski@cciminstitute.com>
- Date: Fri, 1 Aug 2008 16:05:49 -0500
- Cc: openldap-software@openldap.org
- Content-class: urn:content-classes:message
- In-reply-to: <23440281.1871217528948439.JavaMail.root@mail2.sys-net.it>
- References: <C8453C0D9CB4B04596651E7298337A27040C1322@ccim-exchange.cciminstitute.com> <23440281.1871217528948439.JavaMail.root@mail2.sys-net.it>
- Thread-index: AcjzO1gDhDv89X/SSqmuHNSFHElI0QA3eleQ
- Thread-topic: back-sql using varchar keyvals and ids
----- Pierangelo Masarati <ando@sys-net.it> wrote:
>You can modify back-sql.h, defining BACKSQL_ARBITRARY_KEY and recompiling, to allow strings to be >used as keys. Not extensively tested, but should work.
Altered the Fedora SRPM to define BACKSQL_ARBITRARY_KEY, rebuilt the RPMs.
Works as expected with either MS SQL Server or MySQL backends. I was able to successfully replace ldap_entries with a view and use baseObject in slapd.conf
Why isn't this #define on by default? Can this be always on or if not moved to a configuration variable in slapd.conf to turn it on?
Jason Potkanski
Information Technology Developer
CCIM Institute
430 N. Michigan Ave, Suite 800
Chicago, IL 60611-4092
jpotkanski@ccim.com
www.ccim.com
tel: 312.321.8559