[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: back-sql Varchar2 Primary Key Support
- To: Pierangelo Masarati <masarati@aero.polimi.it>
- Subject: Re: back-sql Varchar2 Primary Key Support
- From: "deckrider@gmail.com" <deckrider@gmail.com>
- Date: Fri, 8 May 2009 08:11:47 -0600
- Cc: openldap-software@openldap.org
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=WT30gMjiVdmCspIN9q6PwBtuoxc4hqzWqMpMtxW77Oo=; b=QG5oCR3kb/7Q1uP+7p8w0RPmtUmG7NnoMx9nypxjqNm27ctHjnE9dMTVuwG3xFAGFI fWHlb8EJyNMW8aG6E+yWy2b2G6jHYToLqIb5ud6uFxx8umB67qGyhq45g5b6zGMHMJpj aFCCnGOXX+djAP0gi5vXECaEq/WrX41LtNh9A=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=PNWPNIdXqK3T+TyoCglgxHP940hlUB5SQvz3/lEQoRZbh9k7InmK0/bUqVNg4M0PXE m8btUySfOU6uxft7OBSWMNhP7xxTvUUZyEE5hqzRrs4kta6Hb/MC5SBnlbwYKTysicci yhgC2dgcZorHmgcdlo1wKkhUMZvu9czcfRcgc=
- In-reply-to: <4A043890.7000404@aero.polimi.it>
- References: <20090508132749.GB17190@quandary.is-a-geek.org> <4A043890.7000404@aero.polimi.it>
- User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, May 08, 2009 at 03:50:08PM +0200, Pierangelo Masarati wrote:
> deckrider@gmail.com wrote:
>> Pierangelo Masarati wrote:
>>>> King, Leon C wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Is there a way to wrap oracle functions to where clauses passed
>>>> into back-sql? I have a non-numeric primary key value of my
>>>> users' table which in some cases is preceeded by a '0'. None of
>>>> the data mapped via the ldap_entries.keyval and my table are
>>>> being retrieve when I execute an ldap search. If I remove the
>>>> preceeding '0' the values are retrieved.
>>> Manually edit servers/slapd/back-sql/back-sql.h and #define
>>> BACKSQL_ARBITRARY_KEY (it's #undef'd right now). This allows to use
>>> arbitrary keys (treated as strings) instead of integers. Note: it's not
>>> very well tested, and performances obviously may decrease (lots of
>>> mallocs/frees, more demanding comparisons and so).\
>>
>> I need this also, but get a compile time error:
>>
>> servers/slapd/back-sql/search.c:2420: error: invalid operands to binary
>> << (have ‘struct berval’ and ‘int’)
>
> Please file an ITS <http://www.openldap.org/its/>.
>
> p.
Done: http://www.openldap.org/its/index.cgi/Incoming?id=6100