Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of ole.ersoy@gmail.com designates
 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=som5v06AR5Xs2pQy2RDmz0VROvxXU2J+SxZzGE8ZcTMP/+DYP2MDPlyZmU7vDbDmouIzX9pLfjuwU1Gzqdx0E8dWCmgDiqT/fg0umNCdvEUsYXXlnifgZkjoNySTiSi36u7V4vnBXLz9dK92xIPEXKpCXw/FidrniQJCwnlkftc=
Message-ID: <467D3ABF.6050201@gmail.com>
Date: Sat, 23 Jun 2007 10:22:39 -0500
From: Ole Ersoy <ole.ersoy@gmail.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [Java to LDAP Type Mapping] Double, Long, etc.
References: <467970BB.5030707@gmail.com>
 <46797AD5.6000502@apache.org>	 <4679809E.5000300@gmail.com>
 <4679A76E.7000005@apache.org>
 <a32f6b020706230447m37494899wb334a5568c3244f8@mail.gmail.com>
In-Reply-To: <a32f6b020706230447m37494899wb334a5568c3244f8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Alex Karasulu wrote:
> Using serialization may present issues when trying to figure out how to
> create indices that allow for correct sorting to evaluate ordering 
> assertions
> like for example:
> 
> (foo > 2.95)
> 
> Just a thought.  There's got to be existing data types out there in LDAP
> that map well to Java types that are part of existing published schemas.

Yeah - I was hoping to find something like like this:
http://java.sun.com/j2se/1.3/docs/guide/jdbc/getstart/mapping.html

This has a table that maps sql types to java types.  I did do quite a bit of searching for something similar for LDAP.  Right now the DAS maps everything that is not a Boolean or Integer to the LDAP String syntax, and then restores correct type on a read, much like an IoC container.  Even though this probably covers 90% of the use cases, from a Marketing point of view I think it sounds much better to say that ApacheDS supports decimals and queries on decimals.  Might be something for the road map.

Cheers,
- Ole

SNIP